[TASK] Overhaul extension development kickstarter make (#6231)

Releases: main, 13.4

Author: sarahmccarthy123

Documentation/ExtensionArchitecture/Kickstarter/Make/Index.rst

@@ -12,14 +12,14 @@ Make
 Kickstart a TYPO3 Extension with "Make"
 =======================================
 
-"`Make <https://github.com/b13/make>`__" is a TYPO3 extension provided by b13. It features a quick way to create
-a basic extension scaffold on the console. The extension is available for TYPO3 v10 and above.
+"`Make <https://github.com/b13/make>`__" is a TYPO3 extension provided by b13. It is a quick way to create
+a basic extension scaffold via the console. The extension is available for TYPO3 v10 and above.
 
 1. Install "Make"
 =================
 
 In Composer-based TYPO3 installations you can install the
-extension via Composer, you should install it as :bash:`dev` dependency as
+extension via Composer, but you should install it as a :bash:`dev` dependency as
 it should not be used on production systems:
 
 ..  tabs::
@@ -71,57 +71,57 @@ Call the CLI script on the console:
 3.  Answer the prompt
 =====================
 
-"Make" will now answer some questions that we describe here in-depth:
+"Make" will now ask you the following questions:
 
 `Enter the composer package name (e.g. "vendor/awesome"):`
-    A valid composer package name is defined in the
+    Valid composer package names are defined in the
     `getcomposer name scheme <https://getcomposer.org/doc/04-schema.md#name>`__.
 
-    The vendor **should** be a unique name that is not yet used by other
+    The vendor **should** be a unique name that is not used by any other
     companies or developers.
 
     Example: `my-vendor/my-test`
 
 `Enter the extension key [my_test]:`
-    The extension key **should** follow the rules for best practises on
+    The extension key **should** follow the rules for best practice for
     :ref:`choosing an extension key <extension-key>` if you plan to publish
-    your extension. In most cases, the default, here `my_test`, is sufficient.
+    your extension. In most cases the default, here `my_test`, will be sufficient.
     Press :kbd:`enter` to accept the default or enter another name.
 
 `Enter the PSR-4 namespace [T3docs/MyTest]:`
     The namespace has to be unique within the project. Usually the default
-    should be unique, as your vendor is unique, and you can accept it by
+    will be unique because your vendor name is unique, and you can accept it by
     pressing :kbd:`enter`.
 
 `Choose supported TYPO3 versions (comma separate for multiple) [TYPO3 v11 LTS]:`
-    If you want to support both TYPO3 v11 and v12, enter the following:
+    If you want your extension to be compatible with both TYPO3 v11 and v12, enter:
     `11,12`
 
 `Enter a description of the extension:`
-    A description is mandatory. You can change it later in the file
-    :file:`composer.json <extension-composer-json>` of the extension.
+    A description is mandatory. You can change it later in the
+    :file:`composer.json <extension-composer-json>` extension file.
 
 `Where should the extension be created? [src/extensions/]:`
-    If you have a special path for installing local extensions like
+    If you have a specific folder for your local extensions like
     :file:`packages` enter it here. Otherwise you can accept the
     default.
 
 `May we add a basic service configuration for you? (yes/no) [yes]:`
     If you choose `yes` "Make" will create a basic
-    :file:`Configuration/Services.yaml` to configure :ref:`dependency injection <DependencyInjection>`.
+    :file:`Configuration/Services.yaml` which configures :ref:`dependency injection <DependencyInjection>`.
 
 `May we create a ext_emconf.php for you? (yes/no) [no]:`
     Mandatory for extensions supporting TYPO3 v10. Starting with v11:
-    If your extension should be installable in legacy TYPO3 installations
-    choose `yes`. This is not necessary for local extensions in Composer-based
-    installations.
+    If your extension needs be installable in legacy TYPO3 installations
+    choose `yes`. If your extension is local and in a Composer-based
+    installation it is not necessary and you can choose `no`.
 
 4.  Have a look at the result
 =============================
 
-"Make" created a subfolder under :file:`src/extensions` with the
-composer name (without vendor) of your extension. By default, it contains
-the following files:
+"Make" has now created a subfolder under :file:`src/extensions` with the
+same name as the composer name (without vendor) of your extension. By default
+the subfolder contains the following files:
 
 ..  code-block:: none
     :caption: Page tree of directory :file:`src/extensions`
@@ -137,11 +137,12 @@ the following files:
 5. Install the extension
 ========================
 
-On Composer-based installations the extension is not installed yet.
-It will not be displayed in the :guilabel:`Extension Manager` in the backend.
+On Composer-based installations the extension will be created but not installed.
+Therefore it won't be displayed in the backend :guilabel:`Extension Manager`.
 
-To install it, open the main :file:`composer.json <extension-composer-json>` of your **project** (not the
-one in the created extension) and add the extension directory as new repository:
+To install it, open the main :file:`composer.json <extension-composer-json>` of
+your **project** (not the one in the new extension) and define the extension
+directory as a new repository under `repositories`:
 
 ..  code-block:: json
     :caption: my_project_root/composer.json
@@ -158,8 +159,8 @@ one in the created extension) and add the extension directory as new repository:
         "...": "..."
     }
 
-Then require the extension on Composer-based systems, using the composer
-name defined in the prompt of the script:
+Then, on Composer-based systems, require the extension using the composer
+name:
 
 ..  tabs::
 
@@ -182,7 +183,7 @@ name defined in the prompt of the script:
 6.  Add functionality
 =====================
 
-The following additional commands are available to add more functionality
+The following commands are also available if you want to add more functionality
 to your extension:
 
 *   `make:backendcontroller`  - :ref:`Create a new backend controller <extension-make-backend-controller>`