Imported Upstream version 1.72.0

[platform/upstream/boost.git] / doc / html / boost_process / design.html

diff --git a/doc/html/boost_process/design.html b/doc/html/boost_process/design.html
index 17a65c0..a8442db 100644 (file)
--- a/doc/html/boost_process/design.html
+++ b/doc/html/boost_process/design.html
@@ -47,7 +47,7 @@
 <p>
         <span class="bold"><strong>This library does not try to provide a full library
         for everything process related</strong></span> In many discussions the proposal
-        was made to build boost.process into a DSEL <a href="#ftn.boost_process.design.scope.f0" class="footnote" name="boost_process.design.scope.f0"><sup class="footnote">[27]</sup></a> of some sort. This is not the goal, it rather provides the facilities
+        was made to build boost.process into a DSEL <a href="#ftn.boost_process.design.scope.f0" class="footnote" name="boost_process.design.scope.f0"><sup class="footnote">[29]</sup></a> of some sort. This is not the goal, it rather provides the facilities
         to build such a DSEL-Library on top of it. Therefore the library also does
         <span class="bold"><strong>not</strong></span> force any particular use (such as only
         asynchronous communication) on its user. It rather could be integrated with
@@ -244,7 +244,7 @@
 </div>
 <div class="footnotes">
 <br><hr style="width:100; text-align:left;margin-left: 0">
-<div id="ftn.boost_process.design.scope.f0" class="footnote"><p><a href="#boost_process.design.scope.f0" class="para"><sup class="para">[27] </sup></a>
+<div id="ftn.boost_process.design.scope.f0" class="footnote"><p><a href="#boost_process.design.scope.f0" class="para"><sup class="para">[29] </sup></a>
           Domain Specific Embedded Language
         </p></div>
 </div>