Reword paragraph

docs/components/guidesXml.rst

@@ -46,7 +46,7 @@ Register the new configuration option in the :php:`TreeBuilder` at
 
 Using the tree builder is a topic of itself. Refer to the according symfony documentation.
 
-If the configuration is a setting option to controll the applications workflow you can
+If the configuration is a setting option to control the applications workflow you can
 save it in the :php:class:`phpDocumentor\Guides\Settings\ProjectSettings`. Examples of
 settings options would be `logPath`, `showProgressBar` or `theme`.
 

docs/developers/extensions/structure.rst

@@ -21,26 +21,26 @@ Each Composer package must have a file `composer.json`. See an example here:
     :lineos:
 
 The PHP sources can be found in the directory `src` then as is stated in line 8
-in the `composer.json`. 
+in the `composer.json`.
 
 ..  _extension_symfony:
 
 Create an extension
 ===================
 
 For the PHP package to be an extension you need a class
-extending `\Symfony\Component\DependencyInjection\Extension\Extension` by 
-implementing the interface 
-`Symfony\Component\DependencyInjection\Extension\PrependExtensionInterface` we
-can also add our own configurations to our extension:
+extending `\Symfony\Component\DependencyInjection\Extension\Extension`.
+By implementing the interface
+`Symfony\Component\DependencyInjection\Extension\PrependExtensionInterface`
+you can also configure the guides extension from your extension:
 
 ..  literalinclude:: _YourExtension.php
     :language: php
-    :caption: your-extension/DependencyInjection/YourExtension.php
+    :caption: your-extension/src/DependencyInjection/YourExtension.php
     :lineos:
 
-Lines 24 to 28 load a :ref:`Dependency Injection configuration <extension_di_configuration>` 
-file. Lines 29 to 36 configure the directory overriding the default templates. 
+Lines 24 to 28 load a :ref:`Dependency Injection configuration <extension_di_configuration>`
+file. Lines 29 to 36 configure the directory overriding the default templates.
 Read chapter :ref:`extending_templates` to learn more about this.
 
 ..  note::

docs/developers/extensions/templates.rst

@@ -11,15 +11,15 @@ Register the templates overrides in your extension's
 
 ..  literalinclude:: _YourExtension.php
     :language: php
-    :caption: your-extension/DependencyInjection/YourExtension.php
+    :caption: your-extension/src/DependencyInjection/YourExtension.php
     :lineos:
     :emphasize-lines: 29-35
 
 It is recommended to always extend an existing template so that the Twig files
 of the base templates can be used as fallback for non-defined specific template
 files.
 
-In order to extend the default bootstrap theme, require the according base 
+In order to extend the default bootstrap theme, require the according base
 extension in your extension's `composer.json`:
 
 ..  code-block:: json
@@ -35,12 +35,12 @@ extension in your extension's `composer.json`:
 
 And then set `'extends' => 'bootstrap'` (line 32 in the first code-snippet).
 
-To extend the base template (plain HTML) require `phpdocumentor/guides` in your 
+To extend the base template (plain HTML) require `phpdocumentor/guides` in your
 `composer.json`, and omit the key `extends`:
 
 
 ..  code-block:: php
-    :caption: your-extension/DependencyInjection/YourExtension.php
+    :caption: your-extension/src/DependencyInjection/YourExtension.php
 
     $container->prependExtensionConfig('guides', [
         'themes' => ['mytheme' => dirname(__DIR__, 3) . '/resources/template'],