[pygccxml-commit] SF.net SVN: pygccxml:[1420] pyplusplus_dev/docs/documentation/functions/ call_policies.rest

[<rom...@us...>]

Revision: 1420
          http://pygccxml.svn.sourceforge.net/pygccxml/?rev=1420&view=rev
Author:   roman_yakovenko
Date:     2008-10-05 12:35:30 +0000 (Sun, 05 Oct 2008)

Log Message:
-----------
small cosmetic changes

Modified Paths:
--------------
    pyplusplus_dev/docs/documentation/functions/call_policies.rest

Modified: pyplusplus_dev/docs/documentation/functions/call_policies.rest
===================================================================
--- pyplusplus_dev/docs/documentation/functions/call_policies.rest	2008-10-05 10:05:46 UTC (rev 1419)
+++ pyplusplus_dev/docs/documentation/functions/call_policies.rest	2008-10-05 12:35:30 UTC (rev 1420)
@@ -73,7 +73,7 @@
 --------
 
 `Py++`_ is able to "guess" few call policies, base on analysis of return type
-and\\or operator name:
+and\\or callable name:
 
 * ``default_call_policies``:
 
@@ -134,7 +134,7 @@
 
     /* undefined call policies */
 
-  comment, in place of call policy. If `Py++`_ was wrong and function doesn't
+  comment, instead of call policy. If `Py++`_ was wrong and function doesn't
   need call policy the generate code will compile fine, otherwise you will get a
   compilation error.
 
@@ -153,7 +153,7 @@
 
 Actually you should define ``boost::python::type_id`` specialization also in case
 a function takes the opaque type as an argument. `Py++`_ can do it for you, all
-you need is to say to mark a declaration as opaque.
+you need is to mark a declaration as opaque.
 
 Example:
 


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.