X-Git-Url: https://gerrit.fd.io/r/gitweb?a=blobdiff_plain;f=docs%2Fgettingstarted%2Fdevelopers%2Fgdb_examples.rst;h=71340dabcd0222d07aa8f32a745e7d88cd086c00;hb=005a3331809a4d071bd2a44895fb1a9a800a09f5;hp=b2ef65bcd83f45292e73527a841bec44eca5c542;hpb=a38d001cfe80c29291fb02a02fe8b624562db91c;p=vpp.git

diff --git a/docs/gettingstarted/developers/gdb_examples.rst b/docs/gettingstarted/developers/gdb_examples.rst
index b2ef65bcd83..71340dabcd0 100644
--- a/docs/gettingstarted/developers/gdb_examples.rst
+++ b/docs/gettingstarted/developers/gdb_examples.rst
@@ -10,7 +10,7 @@ In this section we have a few useful gdb commands.
 Starting GDB
 ----------------------------
 
-Once at the gdb prompt VPP can be started with the following:
+Once at the gdb prompt, VPP can be started by running the following commands:
 
 .. code-block:: console
 
@@ -18,14 +18,14 @@ Once at the gdb prompt VPP can be started with the following:
    Starting program: /scratch/vpp-master/build-root/install-vpp_debug-native/vpp/bin/vpp -c /etc/vpp/startup.conf
     [Thread debugging using libthread_db enabled]
     Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
-    vlib_plugin_early_init:361: plugin path /scratch/vpp-master/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins:/scratch/vpp-master/build-root/install-vpp_debug-native/vpp/lib64/vpp_plugins
+    vlib_plugin_early_init:361: plugin path /scratch/vpp-master/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins:/scratch/vpp-master/build-root/install-vpp_debug-native/vpp/lib/vpp_plugins
     ....
 
 Backtrace
 ----------------------------
 
-If you encounter issues when running VPP, such as VPP terminating due to a segfault
-or abort signal, you can run the VPP debug binary and then execute **backtrace** or **bt**.
+If you encounter errors when running VPP, such as VPP terminating due to a segfault
+or abort signal, then you can run the VPP debug binary and then execute **backtrace** or **bt**.
 
 .. code-block:: console
 
@@ -38,12 +38,12 @@ or abort signal, you can run the VPP debug binary and then execute **backtrace**
 Get to the GDB prompt
 ---------------------------------------
 
-When running VPP is running get to the command prompt with CTRL-c.
+When VPP is running, you can get to the command prompt by pressing **CTRL+C**.
 
 Breakpoints
 ---------------------------------------
 
-When at the GDB prompt set a breakpoint like so:
+When at the GDB prompt, set a breakpoint by running the commands below:
 
 .. code-block:: console