[Boost-commit] svn:boost r86746 - trunk/tools/build/v2/doc/src

Subject: [Boost-commit] svn:boost r86746 - trunk/tools/build/v2/doc/src
From: ghost_at_[hidden]
Date: 2013-11-18 01:08:02

Author: vladimir_prus
Date: 2013-11-18 01:08:02 EST (Mon, 18 Nov 2013)
New Revision: 86746
URL: http://svn.boost.org/trac/boost/changeset/86746

Log:
Replace "Boost Build" with "Boost.Build".

Refs #9304.

Text files modified: 
   trunk/tools/build/v2/doc/src/extending.xml |     4 ++--                                    
   trunk/tools/build/v2/doc/src/recipes.xml   |     2 +-                                      
   trunk/tools/build/v2/doc/src/reference.xml |     2 +-                                      
   3 files changed, 4 insertions(+), 4 deletions(-)

Modified: trunk/tools/build/v2/doc/src/extending.xml
==============================================================================
--- trunk/tools/build/v2/doc/src/extending.xml	Mon Nov 18 01:05:56 2013	(r86745)
+++ trunk/tools/build/v2/doc/src/extending.xml	2013-11-18 01:08:02 EST (Mon, 18 Nov 2013)	(r86746)
@@ -181,7 +181,7 @@
         once with the same properties. Returning to different instance of <classname>file-target</classname>
         that correspond to the same file clearly will result in problems. Therefore, whenever
         returning targets you should pass them via the <code>virtual-target.register</code>
-        function, besides allowing Boost Build to track which virtual targets
+        function, besides allowing Boost.Build to track which virtual targets
         got created for each metatarget, this will also replace targets with previously created identical
         ones, as necessary.<footnote><para>This create-then-register pattern is caused by limitations 
         of the Boost.Jam language. Python port is likely to never create duplicate targets.</para></footnote>
@@ -888,7 +888,7 @@
 
                 <listitem><para>if a feature is used to refer to a path relative
                 to the Jamfile, it must be a “path” feature. Such features will
-                also get their values automatically converted to Boost Build's
+                also get their values automatically converted to Boost.Build's
                 internal path representation. For example, <code>include</code>
                 is a path feature.</para></listitem>
 

Modified: trunk/tools/build/v2/doc/src/recipes.xml
==============================================================================
--- trunk/tools/build/v2/doc/src/recipes.xml	Mon Nov 18 01:05:56 2013	(r86745)
+++ trunk/tools/build/v2/doc/src/recipes.xml	2013-11-18 01:08:02 EST (Mon, 18 Nov 2013)	(r86746)
@@ -6,6 +6,6 @@
        future or FAQ completely supercedes it. -->
 
   <appendix id="bbv2.recipies">
-    <title>Boost Build System V2 recipes</title>
+    <title>Boost.Build System V2 recipes</title>
 
   </appendix>

Modified: trunk/tools/build/v2/doc/src/reference.xml
==============================================================================
--- trunk/tools/build/v2/doc/src/reference.xml	Mon Nov 18 01:05:56 2013	(r86745)
+++ trunk/tools/build/v2/doc/src/reference.xml	2013-11-18 01:08:02 EST (Mon, 18 Nov 2013)	(r86746)
@@ -742,7 +742,7 @@
 
           <para>
             <emphasis role="bold">Note:</emphasis> Due to some internal details
-            in the current Boost Build implementation it is not possible to have
+            in the current Boost.Build implementation it is not possible to have
             features whose valid values are all positive integer. As a
             workaround a large set of allowed values has been defined for this
             feature and, if a different one is needed, user can easily add it by