X-Git-Url: http://git.droids-corp.org/?a=blobdiff_plain;f=doc%2Fguides%2Fsample_app_ug%2Ftimer.rst;h=00b69532495e496c7d8681e41d145c40cc5186a7;hb=df1bfde4ff0d;hp=bdd57d947fb434e02ce6116c9126a304dabf5e35;hpb=d0dff9ba445e47199a420dd4b5451ec2860d3d3b;p=dpdk.git

diff --git a/doc/guides/sample_app_ug/timer.rst b/doc/guides/sample_app_ug/timer.rst
index bdd57d947f..00b6953249 100644
--- a/doc/guides/sample_app_ug/timer.rst
+++ b/doc/guides/sample_app_ug/timer.rst
@@ -31,7 +31,7 @@
 Timer Sample Application
 ========================
 
-The Timer sample application is a simple application that demonstrates the use of a timer in an Intel® DPDK application.
+The Timer sample application is a simple application that demonstrates the use of a timer in a DPDK application.
 This application prints some messages from different lcores regularly, demonstrating the use of timers.
 
 Compiling the Application
@@ -41,7 +41,8 @@ Compiling the Application
 
     .. code-block:: console
 
-        export RTE_SDK=/path/to/rte_sdk cd ${RTE_SDK}/examples/timer
+        export RTE_SDK=/path/to/rte_sdk
+        cd ${RTE_SDK}/examples/timer
 
 #.  Set the target (a default target is used if not specified). For example:
 
@@ -49,7 +50,7 @@ Compiling the Application
 
         export RTE_TARGET=x86_64-native-linuxapp-gcc
 
-    See the *Intel® DPDK Getting Started Guide* for possible *RTE_TARGET* values.
+    See the *DPDK Getting Started Guide* for possible *RTE_TARGET* values.
 
 #.  Build the application:
 
@@ -64,9 +65,9 @@ To run the example in linuxapp environment:
 
 .. code-block:: console
 
-    $ ./build/timer -c f -n 4
+    $ ./build/timer -l 0-3 -n 4
 
-Refer to the *Intel® DPDK Getting Started Guide* for general information on running applications and
+Refer to the *DPDK Getting Started Guide* for general information on running applications and
 the Environment Abstraction Layer (EAL) options.
 
 Explanation
@@ -114,7 +115,7 @@ The main loop is very simple in this example:
         /*
          *   Call the timer handler on each core: as we don't
          *   need a very precise timer, so only call
-         *   rte_timer_manage() every ~10ms (at 2 Ghz). In a real
+         *   rte_timer_manage() every ~10ms (at 2 GHz). In a real
          *   application, this will enhance performances as
          *   reading the HPET timer is not efficient.
         */