diff --git a/doc/overriding.html b/doc/overriding.html index 7b28add1..b29bf0e6 100644 --- a/doc/overriding.html +++ b/doc/overriding.html @@ -92,7 +92,7 @@ struct hello_callback : hello

Finally, we add hello_callback to the class_builder<> declaration in our module initialization - function, and when we define the function, we must tell py_cpp about the default + function, and when we define the function, we must tell Boost.Python about the default implementation: 

@@ -120,7 +120,7 @@ hello_class.def(&hello::greet, "greet", &hello_callback::default_gree
     

       *You may ask, "Why do we need this derived
       class? This could have been designed so that everything gets done right
-      inside of hello." One of the goals of py_cpp is to be
+      inside of hello." One of the goals of Boost.Python is to be
       minimally intrusive on an existing C++ design. In principle, it should be
       possible to expose the interface for a 3rd party library without changing
       it. To unintrusively hook into the virtual functions so that a Python