[Boost-commit] svn:boost r7350

From: mconsoni_at_[hidden]
Date: 2007-07-03 13:38:38

Author: mconsoni
Date: 2007-07-03 13:38:36 EDT (Tue, 03 Jul 2007)
New Revision: 7350
URL: http://svn.boost.org/trac/boost/changeset/7350

Log:

- spell checking (thanks ispell!! :) ).

Text files modified: 
   sandbox/libs/extension/doc/info.qbk      |     2 +-                                      
   sandbox/libs/extension/doc/tutorial3.qbk |     2 +-                                      
   sandbox/libs/extension/doc/tutorial4.qbk |     4 ++--                                    
   sandbox/libs/extension/doc/tutorial5.qbk |     4 ++--                                    
   4 files changed, 6 insertions(+), 6 deletions(-)

Modified: sandbox/libs/extension/doc/info.qbk
==============================================================================
--- sandbox/libs/extension/doc/info.qbk	(original)
+++ sandbox/libs/extension/doc/info.qbk	2007-07-03 13:38:36 EDT (Tue, 03 Jul 2007)
@@ -119,7 +119,7 @@
 In the code we could see that add argument is a Info class instance. In this case is =word_description=
 which receives the language and word as arguments.
 
-Now we could start using that information in the main code. Rerieving Info class is easy, you should just call
+Now we could start using that information in the main code. Retrieving Info class is easy, you should just call
 =get_info()= method of the factory. 
 
 Let's see some code using the multilanguage hello world words:

Modified: sandbox/libs/extension/doc/tutorial3.qbk
==============================================================================
--- sandbox/libs/extension/doc/tutorial3.qbk	(original)
+++ sandbox/libs/extension/doc/tutorial3.qbk	2007-07-03 13:38:36 EDT (Tue, 03 Jul 2007)
@@ -109,7 +109,7 @@
 
 \n
 
-It is expected that at this point you can create your own classes with multi-argument contructors and use them via
+It is expected that at this point you can create your own classes with multi-argument constructors and use them via
 Boost.extensions without problems.
 
 [endsect]
\ No newline at end of file

Modified: sandbox/libs/extension/doc/tutorial4.qbk
==============================================================================
--- sandbox/libs/extension/doc/tutorial4.qbk	(original)
+++ sandbox/libs/extension/doc/tutorial4.qbk	2007-07-03 13:38:36 EDT (Tue, 03 Jul 2007)
@@ -63,7 +63,7 @@
 ``
 
 
-Also note that we are using the Info int to store some kind of "version", and then we could diferrentiate the classes
+Also note that we are using the Info int to store some kind of "version", and then we could differentiate the classes
 by its int (see Info class tutorial for more information on this).
 
 ``
@@ -100,7 +100,7 @@
 [^hello world! | v2 hello world! v2 | v2 hello world! v2]]]]
 
 
-The first "hello world" is returned by the first version of the library, and the second and third retruned by the second version.
+The first "hello world" is returned by the first version of the library, and the second and third returned by the second version.
 
 Finally, we will show another example similar to the former but in this case we implement a different interface, same class
 name ('hello') but with different interface ('salute').

Modified: sandbox/libs/extension/doc/tutorial5.qbk
==============================================================================
--- sandbox/libs/extension/doc/tutorial5.qbk	(original)
+++ sandbox/libs/extension/doc/tutorial5.qbk	2007-07-03 13:38:36 EDT (Tue, 03 Jul 2007)
@@ -65,7 +65,7 @@
 ``
 
 Apart from that we need some protocol information like the server address, port or modes. This data is needed for each protocol and
-each protocol maybe could have differente implementations with different servers or ports.
+each protocol maybe could have different implementations with different servers or ports.
 
 Of course our Info class is a perfect solution to store this data. But in this case as the information is needed for each protocol we could
 define a base class as the info class and then implement specific versions for each protocol (at least one, could be more for each protocol).
@@ -127,7 +127,7 @@
 }
 ``
 
-Finally let's use our implementation for an hypotetical connection:
+Finally let's use our implementation for an hypothetical connection:
 
 ``
         std::list<factory< protocol, boost::shared_ptr<network_parameters> > >::iterator current_plugin = factory_list.begin();