Small documentation update.

llvm-svn: 60045

tools/llvmc2/doc/LLVMC-Reference.rst

@@ -41,8 +41,8 @@ language names (which are, in turn, determined from file
 extensions). If you want to force files ending with ".c" to compile as
 C++, use the ``-x`` option, just like you would do it with ``gcc``::
 
-      $ llvmc2 -x c hello.cpp
-      $ # hello.cpp is really a C file
+      $ # hello.c is really a C++ file
+      $ llvmc2 -x c++ hello.c
       $ ./a.out
       hello
 
@@ -361,7 +361,7 @@ Tool-specific option properties like ``append_cmd`` have (obviously)
 no meaning in the context of ``OptionList``, so the only properties
 allowed there are ``help`` and ``required``.
 
-Option lists are used at the file scope. See file
+Option lists are used at file scope. See the file
 ``plugins/Clang/Clang.td`` for an example of ``OptionList`` usage.
 
 .. _hooks:

tools/llvmc2/doc/LLVMC-Tutorial.rst

@@ -23,8 +23,10 @@ much as possible, so most of the familiar options work::
      $ ./a.out
      hello
 
-For further help on command-line LLVMC usage, refer to the ``llvmc
---help`` output.
+This will invoke ``llvm-g++`` under the hood (you can see which
+commands are executed by using the ``-v`` option). For further help on
+command-line LLVMC usage, refer to the ``llvmc --help`` output.
+
 
 Using LLVMC to generate toolchain drivers
 =========================================
@@ -51,7 +53,7 @@ reference manual.
 Contents of the file ``Simple.td`` look like this::
 
     // Include common definitions
-    include "Common.td"
+    include "llvm/CompilerDriver/Common.td"
 
     // Tool descriptions
     def gcc : Tool<