misc: fix name for binaries

Change-Id: Ib9076a0d985049cfc28531381ae940470c2d1bd5

user/bug-report-guide.md

@@ -73,7 +73,7 @@ one already.
     `dl.jami.net`, your own build, etc.).  If you have built your own
     version of Jami, please specify the exact Jami Daemon version and
     client version (you can obtain it using `jamid -v` and
-    `jami-gnome -v` or `jami-qt -v`; but note that our packages are
+    `jami-gnome -v` or `jami -v`; but note that our packages are
     updated quite often) and the Git commit.
   - network conditions: are both devices on the same local network?
     Different networks?  Is one or both behind NAT?
@@ -194,11 +194,11 @@ manually.
        `/usr/lib/x86_64-linux-gnu/jamid -d -c` or
        `/usr/libexec/jamid -d -c`.
 3. In another terminal, start the client, using e.g. `jami-gnome -d`
-   or `jami-qt -d`.
+   or `jami -d`.
 
 To get a backtrace, you can run the program inside GDB:
 
-`gdb -ex run jami-qt`, or `gdb -ex run jami-gnome`, or
+`gdb -ex run --args jami -d`, or `gdb -ex run jami-gnome`, or
 `gdb -ex run --args /usr/libexec/jamid -cd`, depending on the
 component you need to debug.