Merged back from release branch.

Fix up windows doc error [SVN r50810]
HHHHHCS · Jan 27, 2009 · e5f30ae · e5f30ae
1 parent 8828c0b
commit e5f30ae
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/more/getting_started/unix-variants.html b/more/getting_started/unix-variants.html
@@ -431,7 +431,7 @@ <h3><a class="toc-backref" href="#id29">5.2.4&nbsp;&nbsp;&nbsp;Invoke <tt class=
 $ cd ~/<tt class="docutils literal"><span class="pre">boost_1_38_0</span></tt>
 $ bjam <strong>--build-dir=</strong>/tmp/build-boost <strong>--toolset=</strong>gcc stage
 </pre>
-<p>That will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, “``--build-type=complete``”.</p>
+<p>That will build static and shared non-debug multi-threaded variants of the libraries. To build all variants, pass the additional option, “<tt class="docutils literal"><span class="pre">--build-type=complete</span></tt>”.</p>
 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 <!-- Software License, Version 1.0. (See accompanying -->
 <!-- file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt) -->
@@ -461,7 +461,7 @@ <h3><a class="toc-backref" href="#id29">5.2.4&nbsp;&nbsp;&nbsp;Invoke <tt class=
 <p class="last">Boost.Build can produce a great deal of output, which can
 make it easy to miss problems.  If you want to make sure
 everything is went well, you might redirect the output into a
-file by appending “``&gt;build.log 2&gt;&amp;1``” to your command line.</p>
+file by appending “<tt class="docutils literal"><span class="pre">&gt;build.log</span> <span class="pre">2&gt;&amp;1</span></tt>” to your command line.</p>
 </div>
 </div>
 </div>

diff --git a/more/getting_started/windows.html b/more/getting_started/windows.html
@@ -500,7 +500,7 @@ <h3><a class="toc-backref" href="#id39">5.2.4&nbsp;&nbsp;&nbsp;Invoke <tt class=
 C:\WINDOWS&gt; cd <tt class="docutils literal"><span class="pre">C:\Program</span> <span class="pre">Files\boost\</span></tt><tt class="docutils literal"><span class="pre">boost_1_38_0</span></tt>
 <tt class="docutils literal"><span class="pre">C:\Program</span> <span class="pre">Files\boost\</span></tt><tt class="docutils literal"><span class="pre">boost_1_38_0</span></tt>&gt; bjam <strong>^</strong>
 More? <strong>--build-dir=</strong>&quot;C:\Documents and Settings\dave\build-boost&quot; <strong>^</strong>
-More? <strong>--toolset=</strong>msvc <strong>--build-type=complete</strong> stage
+More? <strong>--build-type=complete</strong> <strong>msvc</strong> stage
 </pre>
 <p>Be sure to read <a class="reference internal" href="#continuation">this note</a> about the appearance of <tt class="docutils literal"><span class="pre">^</span></tt>,
 <tt class="docutils literal"><span class="pre">More?</span></tt> and quotation marks (<tt class="docutils literal"><span class="pre">&quot;</span></tt>) in that line.</p>

diff --git a/more/getting_started/windows.rst b/more/getting_started/windows.rst
@@ -215,7 +215,7 @@ For example, your session might look like this: [#continuation]_
    C:\\WINDOWS> cd |default-root|
    |default-root|> bjam **^**
    More? **--build-dir=**\ "C:\\Documents and Settings\\dave\\build-boost" **^**
-   More? **--toolset=**\ msvc **--build-type=complete** stage
+   More? **--build-type=complete** **msvc** stage
 
 Be sure to read `this note`__ about the appearance of ``^``,
 ``More?`` and quotation marks (``"``) in that line.