Imported Upstream version 1.58.0upstream/1.58.0

Change-Id: If0072143aa26874812e0db6872e1efb10a3e5e94
Signed-off-by: DongHun Kwak <dh0128.kwak@samsung.com>

6 files changed, 39 insertions, 39 deletions

diff --git a/more/getting_started/detail/build-from-source-head.rst b/more/getting_started/detail/build-from-source-head.rst
index 6807ab694a..e00e07ebb6 100644
--- a/more/getting_started/detail/build-from-source-head.rst
+++ b/more/getting_started/detail/build-from-source-head.rst
@@ -28,7 +28,7 @@ First, find the toolset corresponding to your compiler in the
 following table (an up-to-date list is always available `in the
 Boost.Build documentation`__).
 
-__ http://www.boost.org/boost-build2/doc/html/bbv2/reference/tools.html
+__ http://www.boost.org/build/doc/html/bbv2/reference/tools.html
 
 .. Note:: If you previously chose a toolset for the purposes of
   `building b2`_, you should assume it won't work and instead
@@ -107,5 +107,5 @@ invoke ``b2`` as follows:
 For a complete description of these and other invocation options,
 please see the `Boost.Build documentation`__.
 
-__ http://www.boost.org/boost-build2/doc/html/bbv2/advanced/invocation.html
+__ http://www.boost.org/build/doc/html/bbv2/overview/invocation.html
 
diff --git a/more/getting_started/detail/build-from-source-tail.rst b/more/getting_started/detail/build-from-source-tail.rst
index dd782ac6c5..b05c6a5dd9 100644
--- a/more/getting_started/detail/build-from-source-tail.rst
+++ b/more/getting_started/detail/build-from-source-tail.rst
@@ -70,4 +70,4 @@ linker, consider setting up a ``user-config.jam`` file as described
 doesn't work for you, please address questions about configuring Boost
 for your compiler to the `Boost.Build mailing list`_.
 
-__ http://www.boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html
+__ http://www.boost.org/build/doc/html/bbv2/overview/configuration.html
diff --git a/more/getting_started/detail/release-variables.rst b/more/getting_started/detail/release-variables.rst
index efb7b80716..f8234a1382 100644
--- a/more/getting_started/detail/release-variables.rst
+++ b/more/getting_started/detail/release-variables.rst
@@ -5,8 +5,8 @@
 .. This file contains all the definitions that need to be updated
 .. for each new release of Boost.
 
-.. |boost-version-number| replace:: 1.57.0
-.. |boost_ver| replace:: ``boost_1_57_0``
-.. |boost_ver-bold| replace:: **boost_1_57_0**
+.. |boost-version-number| replace:: 1.58.0
+.. |boost_ver| replace:: ``boost_1_58_0``
+.. |boost_ver-bold| replace:: **boost_1_58_0**
 
-.. _sf-download: http://www.boost.org/users/history/version_1_57_0.html
+.. _sf-download: http://www.boost.org/users/history/version_1_58_0.html
diff --git a/more/getting_started/unix-variants.html b/more/getting_started/unix-variants.html
index a13c20b94a..aa0e18d140 100644
--- a/more/getting_started/unix-variants.html
+++ b/more/getting_started/unix-variants.html
@@ -61,14 +61,14 @@
 <div class="section" id="get-boost">
 <h1><a class="toc-backref" href="#id19">1&nbsp;&nbsp;&nbsp;Get Boost</a></h1>
 <p>The most reliable way to get a copy of Boost is to download a
-distribution from <a class="reference external" href="http://www.boost.org/users/history/version_1_57_0.html">SourceForge</a>:</p>
+distribution from <a class="reference external" href="http://www.boost.org/users/history/version_1_58_0.html">SourceForge</a>:</p>
 <ol class="arabic">
-<li><p class="first">Download <a class="reference external" href="http://www.boost.org/users/history/version_1_57_0.html"><tt class="docutils literal">boost_1_57_0</tt><tt class="docutils literal">.tar.bz2</tt></a>.</p>
+<li><p class="first">Download <a class="reference external" href="http://www.boost.org/users/history/version_1_58_0.html"><tt class="docutils literal">boost_1_58_0</tt><tt class="docutils literal">.tar.bz2</tt></a>.</p>
 </li>
 <li><p class="first">In the directory where you want to put the Boost installation,
 execute</p>
 <pre class="literal-block">
-tar --bzip2 -xf <em>/path/to/</em><tt class="docutils literal">boost_1_57_0</tt>.tar.bz2
+tar --bzip2 -xf <em>/path/to/</em><tt class="docutils literal">boost_1_58_0</tt>.tar.bz2
 </pre>
 </li>
 </ol>
@@ -81,7 +81,7 @@ creators usually choose to break Boost up into several packages,
 reorganize the directory structure of the Boost distribution,
 and/or rename the library binaries.<a class="footnote-reference" href="#packagers" id="id2"><sup>1</sup></a> If you have
 any trouble, we suggest using an official Boost distribution
-from <a class="reference external" href="http://www.boost.org/users/history/version_1_57_0.html">SourceForge</a>.</p>
+from <a class="reference external" href="http://www.boost.org/users/history/version_1_58_0.html">SourceForge</a>.</p>
 </div>
 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 <!-- Software License, Version 1.0. (See accompanying -->
@@ -91,7 +91,7 @@ from <a class="reference external" href="http://www.boost.org/users/history/vers
 <h1><a class="toc-backref" href="#id20">2&nbsp;&nbsp;&nbsp;The Boost Distribution</a></h1>
 <p>This is a sketch of the resulting directory structure:</p>
 <pre class="literal-block">
-<strong>boost_1_57_0</strong><strong>/</strong> .................<em>The “boost root directory”</em>
+<strong>boost_1_58_0</strong><strong>/</strong> .................<em>The “boost root directory”</em>
    <strong>index.htm</strong> .........<em>A copy of www.boost.org starts here</em>
    <strong>boost</strong><strong>/</strong> .........................<em>All Boost Header files</em>
    <tt class="docutils literal"> </tt>
@@ -136,7 +136,7 @@ anything you can use in these directories.</p>
 </div>
 <p>It's important to note the following:</p>
 <ol class="arabic" id="boost-root-directory">
-<li><p class="first">The path to the <strong>boost root directory</strong> (often <tt class="docutils literal">/usr/local/</tt><tt class="docutils literal">boost_1_57_0</tt>) is
+<li><p class="first">The path to the <strong>boost root directory</strong> (often <tt class="docutils literal">/usr/local/</tt><tt class="docutils literal">boost_1_58_0</tt>) is
 sometimes referred to as <tt class="docutils literal">$BOOST_ROOT</tt> in documentation and
 mailing lists .</p>
 </li>
@@ -245,7 +245,7 @@ int main()
 <p>Now, in the directory where you saved <tt class="docutils literal">example.cpp</tt>, issue the
 following command:</p>
 <pre class="literal-block">
-c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_57_0</tt> example.cpp -o example
+c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_58_0</tt> example.cpp -o example
 </pre>
 <p>To test the result, type:</p>
 <pre class="literal-block">
@@ -276,7 +276,7 @@ you'll need to acquire library binaries.</p>
 <p>Issue the following commands in the shell (don't type <tt class="docutils literal">$</tt>; that
 represents the shell's prompt):</p>
 <pre class="literal-block">
-<strong>$</strong> cd <em>path/to/</em><tt class="docutils literal">boost_1_57_0</tt>
+<strong>$</strong> cd <em>path/to/</em><tt class="docutils literal">boost_1_58_0</tt>
 <strong>$</strong> ./bootstrap.sh --help
 </pre>
 <p>Select your configuration options and invoke <tt class="docutils literal">./bootstrap.sh</tt> again
@@ -330,7 +330,7 @@ the directory where you want Boost.Build to be installed</li>
 <div class="section" id="identify-your-toolset">
 <span id="toolset-name"></span><span id="toolset"></span><h3><a class="toc-backref" href="#id28">5.2.2&nbsp;&nbsp;&nbsp;Identify Your Toolset</a></h3>
 <p>First, find the toolset corresponding to your compiler in the
-following table (an up-to-date list is always available <a class="reference external" href="http://www.boost.org/boost-build2/doc/html/bbv2/reference/tools.html">in the
+following table (an up-to-date list is always available <a class="reference external" href="http://www.boost.org/build/doc/html/bbv2/reference/tools.html">in the
 Boost.Build documentation</a>).</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
@@ -425,10 +425,10 @@ invoke <tt class="docutils literal">b2</tt> as follows:</p>
 b2 <strong>--build-dir=</strong><a class="reference internal" href="#id10"><em>build-directory</em></a> <strong>toolset=</strong><a class="reference internal" href="#toolset-name"><em>toolset-name</em></a> <tt class="docutils literal"> </tt> stage
 </pre>
 <p>For a complete description of these and other invocation options,
-please see the <a class="reference external" href="http://www.boost.org/boost-build2/doc/html/bbv2/advanced/invocation.html">Boost.Build documentation</a>.</p>
+please see the <a class="reference external" href="http://www.boost.org/build/doc/html/bbv2/overview/invocation.html">Boost.Build documentation</a>.</p>
 <p>For example, your session might look like this:</p>
 <pre class="literal-block">
-$ cd ~/<tt class="docutils literal">boost_1_57_0</tt>
+$ cd ~/<tt class="docutils literal">boost_1_58_0</tt>
 $ b2 <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, “<tt class="docutils literal"><span class="pre">--build-type=complete</span></tt>”.</p>
@@ -499,7 +499,7 @@ packages for libz and libbz2 if you need those features.  Other
 errors when building Boost libraries are cause for concern.</p>
 <p>If it seems like the build system can't find your compiler and/or
 linker, consider setting up a <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file as described
-<a class="reference external" href="http://www.boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html">here</a>.  If that isn't your problem or the <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file
+<a class="reference external" href="http://www.boost.org/build/doc/html/bbv2/overview/configuration.html">here</a>.  If that isn't your problem or the <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file
 doesn't work for you, please address questions about configuring Boost
 for your compiler to the <a class="reference external" href="http://www.boost.org/more/mailing_lists.htm#jamboost">Boost.Build mailing list</a>.</p>
 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
@@ -544,14 +544,14 @@ project.</li>
 <ol class="upperalpha">
 <li><p class="first">You can specify the full path to each library:</p>
 <pre class="literal-block">
-$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_57_0</tt> example.cpp -o example <strong>\</strong>
+$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_58_0</tt> example.cpp -o example <strong>\</strong>
    <strong>~/boost/stage/lib/libboost_regex-gcc34-mt-d-1_36.a</strong>
 </pre>
 </li>
 <li><p class="first">You can separately specify a directory to search (with <tt class="docutils literal"><span class="pre">-L</span></tt><em>directory</em>) and a library name to search for (with <tt class="docutils literal"><span class="pre">-l</span></tt><em>library</em>,<a class="footnote-reference" href="#lowercase-l" id="id14"><sup>2</sup></a> dropping the filename's leading <tt class="docutils literal">lib</tt> and trailing
 suffix (<tt class="docutils literal">.a</tt> in this case):</p>
 <pre class="literal-block">
-$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_57_0</tt> example.cpp -o example <strong>\</strong>
+$ c++ -I <em>path/to/</em><tt class="docutils literal">boost_1_58_0</tt> example.cpp -o example <strong>\</strong>
    <strong>-L~/boost/stage/lib/ -lboost_regex-gcc34-mt-d-1_36</strong>
 </pre>
 <p>As you can see, this method is just as terse as method A for one
diff --git a/more/getting_started/windows.html b/more/getting_started/windows.html
index b2d05979a5..eb4004d6f3 100644
--- a/more/getting_started/windows.html
+++ b/more/getting_started/windows.html
@@ -61,7 +61,7 @@ not supported—they may or may not work.</p>
 <div class="section" id="get-boost">
 <h1><a class="toc-backref" href="#id27">1&nbsp;&nbsp;&nbsp;Get Boost</a></h1>
 <p>The most reliable way to get a copy of Boost is to
-download <a class="reference external" href="http://www.boost.org/users/history/version_1_57_0.html"><tt class="docutils literal">boost_1_57_0</tt><tt class="docutils literal">.7z</tt></a> or <a class="reference external" href="http://www.boost.org/users/history/version_1_57_0.html"><tt class="docutils literal">boost_1_57_0</tt><tt class="docutils literal">.zip</tt></a> and unpack it to install a complete Boost
+download <a class="reference external" href="http://www.boost.org/users/history/version_1_58_0.html"><tt class="docutils literal">boost_1_58_0</tt><tt class="docutils literal">.7z</tt></a> or <a class="reference external" href="http://www.boost.org/users/history/version_1_58_0.html"><tt class="docutils literal">boost_1_58_0</tt><tt class="docutils literal">.zip</tt></a> and unpack it to install a complete Boost
 distribution.<a class="footnote-reference" href="#zip" id="id2"><sup>1</sup></a></p>
 <!-- Copyright David Abrahams 2006. Distributed under the Boost -->
 <!-- Software License, Version 1.0. (See accompanying -->
@@ -71,7 +71,7 @@ distribution.<a class="footnote-reference" href="#zip" id="id2"><sup>1</sup></a>
 <h1><a class="toc-backref" href="#id28">2&nbsp;&nbsp;&nbsp;The Boost Distribution</a></h1>
 <p>This is a sketch of the resulting directory structure:</p>
 <pre class="literal-block">
-<strong>boost_1_57_0</strong><strong>\</strong> .................<em>The “boost root directory”</em>
+<strong>boost_1_58_0</strong><strong>\</strong> .................<em>The “boost root directory”</em>
    <strong>index.htm</strong> .........<em>A copy of www.boost.org starts here</em>
    <strong>boost</strong><strong>\</strong> .........................<em>All Boost Header files</em>
    <strong>lib</strong><strong>\</strong> .....................<em>precompiled library binaries</em>
@@ -116,7 +116,7 @@ anything you can use in these directories.</p>
 </div>
 <p>It's important to note the following:</p>
 <ol class="arabic" id="boost-root-directory">
-<li><p class="first">The path to the <strong>boost root directory</strong> (often <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_57_0</tt>) is
+<li><p class="first">The path to the <strong>boost root directory</strong> (often <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_58_0</tt>) is
 sometimes referred to as <tt class="docutils literal">$BOOST_ROOT</tt> in documentation and
 mailing lists .</p>
 </li>
@@ -255,7 +255,7 @@ cd <em>path</em>\<em>to</em>\<em>some</em>\<em>directory</em>
 </pre>
 <p>followed by Return.  For example,</p>
 <pre class="literal-block">
-cd <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_57_0</tt>
+cd <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_58_0</tt>
 </pre>
 <p class="last">Long commands can be continued across several lines by typing a
 caret (<tt class="docutils literal">^</tt>) at the end of all but the last line.  Some examples
@@ -280,7 +280,7 @@ select <em>Properties</em> from the resulting pop-up menu</p>
 <li><p class="first">In <em>Configuration Properties</em> &gt; <em>C/C++</em> &gt; <em>General</em> &gt; <em>Additional Include
 Directories</em>, enter the path to the Boost root directory, for example</p>
 <blockquote>
-<p><tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_57_0</tt></p>
+<p><tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_58_0</tt></p>
 </blockquote>
 </li>
 <li><p class="first">In <em>Configuration Properties</em> &gt; <em>C/C++</em> &gt; <em>Precompiled Headers</em>, change
@@ -318,7 +318,7 @@ Visual Studio compiler.  In that window, set the <a class="reference internal" h
 directory</a> to a suitable location for creating some temporary
 files and type the following command followed by the Return key:</p>
 <pre class="literal-block">
-cl /EHsc /I <em>path\to\</em><tt class="docutils literal">boost_1_57_0</tt> <em>path</em>\<em>to</em>\example.cpp
+cl /EHsc /I <em>path\to\</em><tt class="docutils literal">boost_1_58_0</tt> <em>path</em>\<em>to</em>\example.cpp
 </pre>
 <p>To test the result, type:</p>
 <pre class="literal-block">
@@ -357,7 +357,7 @@ bootstrap
 </pre>
 <p>The first command prepares the Boost.Build system for use. The second
 command invokes Boost.Build to build the separately-compiled Boost
-libraries. Please consult the <a class="reference external" href="http://www.boost.org/boost-build2/doc/html/bbv2/overview/invocation.html">Boost.Build documentation</a> for a list
+libraries. Please consult the <a class="reference external" href="http://www.boost.org/build/doc/html/bbv2/overview/invocation.html">Boost.Build documentation</a> for a list
 of allowed options.</p>
 </div>
 <div class="section" id="or-build-binaries-from-source">
@@ -389,7 +389,7 @@ the directory where you want Boost.Build to be installed</li>
 <div class="section" id="identify-your-toolset">
 <span id="toolset-name"></span><span id="toolset"></span><h3><a class="toc-backref" href="#id38">5.2.2&nbsp;&nbsp;&nbsp;Identify Your Toolset</a></h3>
 <p>First, find the toolset corresponding to your compiler in the
-following table (an up-to-date list is always available <a class="reference external" href="http://www.boost.org/boost-build2/doc/html/bbv2/reference/tools.html">in the
+following table (an up-to-date list is always available <a class="reference external" href="http://www.boost.org/build/doc/html/bbv2/reference/tools.html">in the
 Boost.Build documentation</a>).</p>
 <div class="note">
 <p class="first admonition-title">Note</p>
@@ -487,11 +487,11 @@ invoke <tt class="docutils literal">b2</tt> as follows:</p>
 b2 <strong>--build-dir=</strong><a class="reference internal" href="#id12"><em>build-directory</em></a> <strong>toolset=</strong><a class="reference internal" href="#toolset-name"><em>toolset-name</em></a> <strong>--build-type=complete</strong> stage
 </pre>
 <p>For a complete description of these and other invocation options,
-please see the <a class="reference external" href="http://www.boost.org/boost-build2/doc/html/bbv2/advanced/invocation.html">Boost.Build documentation</a>.</p>
+please see the <a class="reference external" href="http://www.boost.org/build/doc/html/bbv2/overview/invocation.html">Boost.Build documentation</a>.</p>
 <p>For example, your session might look like this:<a class="footnote-reference" href="#continuation" id="id14"><sup>3</sup></a></p>
 <pre class="literal-block">
-C:\WINDOWS&gt; cd <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_57_0</tt>
-<tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_57_0</tt>&gt; b2 <strong>^</strong>
+C:\WINDOWS&gt; cd <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_58_0</tt>
+<tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_58_0</tt>&gt; b2 <strong>^</strong>
 More? <strong>--build-dir=</strong>&quot;C:\Documents and Settings\dave\build-boost&quot; <strong>^</strong>
 More? <strong>--build-type=complete</strong> <strong>msvc</strong> stage
 </pre>
@@ -568,7 +568,7 @@ packages for libz and libbz2 if you need those features.  Other
 errors when building Boost libraries are cause for concern.</p>
 <p>If it seems like the build system can't find your compiler and/or
 linker, consider setting up a <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file as described
-<a class="reference external" href="http://www.boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html">here</a>.  If that isn't your problem or the <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file
+<a class="reference external" href="http://www.boost.org/build/doc/html/bbv2/overview/configuration.html">here</a>.  If that isn't your problem or the <tt class="docutils literal"><span class="pre">user-config.jam</span></tt> file
 doesn't work for you, please address questions about configuring Boost
 for your compiler to the <a class="reference external" href="http://www.boost.org/more/mailing_lists.htm#jamboost">Boost.Build mailing list</a>.</p>
 <span class="target" id="auto-linking"></span><!-- Copyright David Abrahams 2006. Distributed under the Boost -->
@@ -630,7 +630,7 @@ earlier:</p>
 select <em>Properties</em> from the resulting pop-up menu</li>
 <li>In <em>Configuration Properties</em> &gt; <em>Linker</em> &gt; <em>Additional Library
 Directories</em>, enter the path to the Boost binaries,
-e.g. <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_57_0</tt><tt class="docutils literal">\lib\</tt>.</li>
+e.g. <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_58_0</tt><tt class="docutils literal">\lib\</tt>.</li>
 <li>From the <em>Build</em> menu, select <em>Build Solution</em>.</li>
 </ol>
 <p><a class="reference internal" href="#test-your-program"><em>skip to the next step</em></a></p>
@@ -640,10 +640,10 @@ e.g. <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boos
 <p>For example, we can compile and link the above program from the
 Visual C++ command-line by simply adding the <strong>bold</strong> text below to
 the command line we used earlier, assuming your Boost binaries are
-in <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_57_0</tt><tt class="docutils literal">\lib</tt>:</p>
+in <tt class="docutils literal"><span class="pre">C:\Program</span> Files\boost\</tt><tt class="docutils literal">boost_1_58_0</tt><tt class="docutils literal">\lib</tt>:</p>
 <pre class="literal-block">
-cl /EHsc /I <em>path\to\</em><tt class="docutils literal">boost_1_57_0</tt> example.cpp   <strong>^</strong>
-     <strong>/link /LIBPATH:</strong><strong>C:\Program Files\boost\</strong><strong>boost_1_57_0</strong><strong>\lib</strong>
+cl /EHsc /I <em>path\to\</em><tt class="docutils literal">boost_1_58_0</tt> example.cpp   <strong>^</strong>
+     <strong>/link /LIBPATH:</strong><strong>C:\Program Files\boost\</strong><strong>boost_1_58_0</strong><strong>\lib</strong>
 </pre>
 </div>
 <div class="section" id="library-naming">
@@ -799,7 +799,7 @@ mailing list</a>.</p>
 <colgroup><col class="label" /><col /></colgroup>
 <tbody valign="top">
 <tr><td class="label"><a class="fn-backref" href="#id2">[1]</a></td><td>We recommend
-downloading <a class="reference external" href="http://www.boost.org/users/history/version_1_57_0.html"><tt class="docutils literal">boost_1_57_0</tt><tt class="docutils literal">.7z</tt></a> and using <a class="reference external" href="http://www.7-zip.org">7-Zip</a> to decompress
+downloading <a class="reference external" href="http://www.boost.org/users/history/version_1_58_0.html"><tt class="docutils literal">boost_1_58_0</tt><tt class="docutils literal">.7z</tt></a> and using <a class="reference external" href="http://www.7-zip.org">7-Zip</a> to decompress
 it.  We no longer recommend .zip files for Boost because they are twice
 as large as the equivalent .7z files.  We don't recommend using Windows'
 built-in decompression as it can be painfully slow for large archives.</td></tr>
diff --git a/more/getting_started/windows.rst b/more/getting_started/windows.rst
index 29d5b5ea2f..261ff0f09b 100644
--- a/more/getting_started/windows.rst
+++ b/more/getting_started/windows.rst
@@ -183,7 +183,7 @@ command invokes Boost.Build to build the separately-compiled Boost
 libraries. Please consult the `Boost.Build documentation`__ for a list
 of allowed options.
 
-__ http://www.boost.org/boost-build2/doc/html/bbv2/overview/invocation.html
+__ http://www.boost.org/build/doc/html/bbv2/overview/invocation.html
 
 Or, Build Binaries From Source
 ------------------------------