@@ -24,14 +24,14 @@ Use the following Docker command to render your documentation guide locally:
2424
2525.. include :: /_Includes/_LocalRendering.rst.txt
2626
27- The :ref: `render-documentation-with-docker ` has more information.
27+ See :ref: `render-documentation-with-docker ` for more information.
2828
2929.. _how-to-start-docs-extension :
3030
3131Use the init command to create the Documentation folder
3232=======================================================
3333
34- The following Docker command helps you to create some basic documentation
34+ The following Docker command creates some basic documentation
3535including the required configuration file :file: `Documentation/guides.xml `:
3636
3737.. include :: /_Includes/_InitCommand.rst.txt
@@ -40,15 +40,15 @@ The command creates a folder :path:`Documentation` in the directory it is called
4040from. This should be the root directory of your extension containing the
4141`composer.json <https://docs.typo3.org/permalink/t3coreapi:files-composer-json >`_.
4242
43- Follow the interactive dialoge . We suggest to use the option ReStructuredText (rst)
43+ Follow the interactive dialog . We suggest to use the option ReStructuredText (rst)
4444as this format provides the full power of the TYPO3 documentation theme. Using
4545Markdown (md) is an option for simple and quick one page documentation.
4646
4747If your extension offers a main `Site set <https://docs.typo3.org/permalink/t3coreapi:site-sets >`_
4848enter its name and path when prompted. This will regenerate ready to use
4949documentation about configuration for you. If you have more then one set you
5050can document the other sets manually. If you have no set, you need to write
51- the chapter your self .
51+ the chapter yourself .
5252
5353Make changes and try :ref: `rendering <rendering-docs >` the new documentation.
5454
0 commit comments