Index: docs/quickstart.rst
===================================================================
--- docs/quickstart.rst
+++ docs/quickstart.rst
@@ -62,7 +62,7 @@
 #. Execute the ``lnt runtest test-suite`` test producer, point it at the test suite and
    the compiler you want to test::
 
-   $ lnt runtest test-suite \
+     lnt runtest test-suite \
        --sandbox /tmp/BAR \
        --cc ~/llvm.obj.64/Release+Asserts/bin/clang \
        --cxx ~/llvm.obj.64/Release+Asserts/bin/clang++ \
Index: docs/tests.rst
===================================================================
--- docs/tests.rst
+++ docs/tests.rst
@@ -22,16 +22,16 @@
 server. To set up a one-off server for testing::
 
   # Create a new installation in /tmp/FOO.
-  $ lnt create /tmp/FOO
+  lnt create /tmp/FOO
   created LNT configuration in '/tmp/FOO'
   ...
 
   # Run a local LNT server.
-  $ lnt runserver /tmp/FOO &> /tmp/FOO/runserver.log &
+  lnt runserver /tmp/FOO &> /tmp/FOO/runserver.log &
   [2] 69694
 
   # Watch the server log.
-  $ tail -f /tmp/FOO/runserver.log
+  tail -f /tmp/FOO/runserver.log
   * Running on http://localhost:8000/
   ...
 
@@ -66,8 +66,8 @@
 
 Running the test-suite via CMake and lit uses a different LNT test::
 
-  $ rm -rf /tmp/BAR
-  $ lnt runtest test-suite \
+  rm -rf /tmp/BAR
+  lnt runtest test-suite \
        --sandbox /tmp/BAR \
        --cc ~/llvm.obj.64/Release+Asserts/bin/clang \
        --cxx ~/llvm.obj.64/Release+Asserts/bin/clang++ \
@@ -123,8 +123,8 @@
 The following command shows an example of running the ``nt`` test suite on a
 local build::
 
-  $ rm -rf /tmp/BAR
-  $ lnt runtest nt \
+  rm -rf /tmp/BAR
+  lnt runtest nt \
        --sandbox /tmp/BAR \
        --cc ~/llvm.obj.64/Release+Asserts/bin/clang \
        --cxx ~/llvm.obj.64/Release+Asserts/bin/clang++ \
@@ -160,7 +160,7 @@
 directory. This report can now be submitted directly to an LNT server. For
 example, if we have a local server running as described earlier, we can run::
 
-  $ lnt submit http://localhost:8000/submitRun \
+  lnt submit http://localhost:8000/submitRun \
       /tmp/BAR/test-2010-04-17_23-46-40/report.json
   STATUS: 0
 
@@ -269,7 +269,7 @@
 typical command line using this for evaluating the performance of generated
 code looks something like the following::
 
-  $ lnt runtest test-suite \
+  lnt runtest test-suite \
        --sandbox SANDBOX \
        --cc ~/bin/clang \
        --use-cmake=/usr/local/bin/cmake \
@@ -304,7 +304,7 @@
 
 Full example using ``llvmlab`` to debug a performance improvement::
 
-  $ llvmlab bisect --min-rev=261265 --max-rev=261369 \
+  llvmlab bisect --min-rev=261265 --max-rev=261369 \
     lnt runtest test-suite \
       --cc '%(path)s/bin/clang' \
       --sandbox SANDBOX \
@@ -322,7 +322,7 @@
 The test-suite module can produce a diagnostic report which might be useful
 for figuring out what is going on with a benchmark::
 
-  $ lnt runtest test-suite \
+  lnt runtest test-suite \
          --sandbox /tmp/BAR \
          --cc ~/llvm.obj.64/Release+Asserts/bin/clang \
          --cxx ~/llvm.obj.64/Release+Asserts/bin/clang++ \
@@ -349,7 +349,7 @@
 An example command line for cross-compiling on an X86 machine, targeting
 AArch64 linux, is::
 
-  $ lnt runtest test-suite \
+  lnt runtest test-suite \
          --sandbox SANDBOX \
          --test-suite /work/llvm-test-suite \
          --use-lit lit \
@@ -369,7 +369,7 @@
 metadata for the json report. An example is below. The important keywords to
 make the variables appear in the CMakeCache.txt are "CACHE STRING "" FORCE"::
 
-  $ cat clang_aarch64_linux.cmake
+  cat clang_aarch64_linux.cmake
   set(CMAKE_SYSTEM_NAME Linux )
   set(triple aarch64-linux-gnu )
   set(CMAKE_C_COMPILER /home/user/build/bin/clang CACHE STRING "" FORCE)