Removed outdated deprecation notes in docs.

sir-sigurd · sir-sigurd · commit a03ad20b740b · 2017-11-14T22:33:24.000+05:00
diff --git a/docs/how_to/apphooks.rst b/docs/how_to/apphooks.rst
@@ -22,10 +22,6 @@ The basics of apphook creation
 
 To create an apphook, create a ``cms_apps.py`` file in your application.
 
-.. note:: Up to version 3.1 this module was named ``cms_app.py`` - please
-          update your existing modules to the new naming convention.
-          Support for the old name will be removed in version 3.4.
-
 The file needs to contain a :class:`CMSApp <cms.app_base.CMSApp>` sub-class. For example::
 
     from cms.app_base import CMSApp
diff --git a/docs/how_to/menus.rst b/docs/how_to/menus.rst
@@ -39,10 +39,6 @@ Create a ``cms_menus.py`` in your application, with the following::
 
     menu_pool.register_menu(TestMenu)
 
-.. note:: Up to version 3.1 this module was named ``menu.py``. Please
-          update your existing modules to the new naming convention.
-          Support for the old name will be removed in version 3.4.
-
 If you refresh a page you should now see the menu entries above.
 The ``get_nodes`` function should return a list of
 :class:`NavigationNode <menus.base.NavigationNode>` instances. A
diff --git a/docs/how_to/toolbar.rst b/docs/how_to/toolbar.rst
@@ -77,10 +77,6 @@ A simple example, registering a class that does nothing::
             pass
 
 
-.. note:: Up to version 3.1 the module was named ``cms_toolbar.py``. Please
-          update your existing modules to the new naming convention.
-          Support for the old name will be removed in version 3.4.
-
 .. warning::
 
     As the toolbar passed to ``post_template_populate`` has been already populated with items from
