Rename tutorials and restore Custom Frontend Component name (without the 'CMS')

Author: marbru

docs/source/tutorial/custom_components.rst

@@ -1,15 +1,15 @@
 .. _custom_components:
 
 #######################################
-Building Custom CMS Frontend Components
+Building Custom Components With Form Classes
 #######################################
 
 .. index::
     single: Custom frontend components
 
 .. versionadded:: 2.0
 
-In this tutorial, we will explore how to create custom **CMS Frontend Components**. These are more
+In this tutorial, we will explore how to create custom **Frontend Components**. These are more
 versatile than :ref:`template_components`, but require some minimal Python coding.
 
 You create a custom frontend component by subclassing the ``CMSFrontendComponent`` class to 
@@ -21,7 +21,7 @@ Hero CMS component example
 ==========================
 
 In this tutorial we will create again a **Hero component** similar to the one in the
-:ref:`previous chapter <template_components>`, but this time via code.
+:ref:`previous chapter <template_components>`.
 
 Directory Structure
 -------------------

docs/source/tutorial/index.rst

@@ -23,7 +23,7 @@ that gets the job done for your project.
    needed. This is the fastest approach to create ``djangocms-frontend`` components.
    Template-based (or auto) components are auto-detected.
 
-3. **Custom CMS Frontend Component** development – A more advanced method that lets you create
+3. **Custom Frontend Component** development – A more advanced method that lets you create
    custom components with **minimal code**. This approach is more flexible than the
    template-based method, but requires some Python coding providing more control over
    the components add and change forms, for example.

docs/source/tutorial/template_components.rst

@@ -1,7 +1,7 @@
 .. _template_components:
 
 ############################
-Building Template Components
+Simplified Component Creation with Templates
 ############################
 
 .. index::
@@ -265,7 +265,7 @@ Template components are a powerful tool for developers, but they have some limit
   Classes are instantiated by default, for example. This is ok for ``widget=forms.Textarea``, but potentially not
   for more complex cases.
 
-For more powerful customization options, consider building a :ref:`custom CMS Frontend Component <custom_components>`
+For more powerful customization options, consider building a :ref:`custom Frontend Component <custom_components>`
 or a :ref:`custom Plugin<how-to-add-frontend-plugins>`