TASK: Improve grammar and syntax a bit

Relates to #92

Documentation/Extbase/Index.rst

@@ -22,8 +22,8 @@ If you develop an extension for TYPO3 you should most definitely use Extbase.
 The days of piBased extensions are numbered. Extbase gives you the benefit of a
 modern, clear and highly structured means of PHP development.
 
-How do I get started with Extbase?
-----------------------------------
+How to get started with Extbase
+-------------------------------
 
 * Check out the Extbase documentation section.
 * Inspect the code of Extbase-based extensions in the The TYPO3 extension repository (TER).

Documentation/Fluid/Index.rst

@@ -22,40 +22,41 @@ projects without TYPO3.
 Should I use Fluid?
 ---------------------
 
-Fluid is the de-facto-standard for any HTML based output in TYPO3. It's used by
-Extbase-Extensions by default and is available to TypoScript via
+Fluid is the de-facto standard for any HTML based output in TYPO3. It's used by
+Extbase Extensions by default and is available in TypoScript via
 :ref:`t3tsref:cobj-fluidtemplate`.
 
-Also you can use the :php:`TYPO3\CMS\Fluid\View\StandaloneView` to use Fluid in your
-command controller or `AbstractPlugin`.
+It is used by the system extension ext:fluid_styled_content, as well, to provide
+output of default content elements.
 
-Also it's used by the system extension fluid_styled_content to provide output of
-default content elements.
+There is even a standalone version of Fluid available,
+:php:`TYPO3\CMS\Fluid\View\StandaloneView`, that provides all the means to use Fluid
+in a command controller or :php:`AbstractPlugin`.
 
-How do I get started with Fluid?
-----------------------------------
+How to get started with Fluid
+-----------------------------
 
 * Check out the Fluid documentation https://github.com/TYPO3/Fluid
 * Check out the Fluid documentation section in this guide.
 * Inspect the existing Fluid templates, e.g. provided by TYPO3's system extension
-  fluid_styled_content https://github.com/TYPO3-CMS/fluid_styled_content .
+  ext:fluid_styled_content https://github.com/TYPO3-CMS/fluid_styled_content .
 
 Concepts
 --------
 
 TYPO3 itself requires the Fluid template engine. As this engine does not know
 anything about TYPO3, the engine is extended by TYPO3 within the system extension
-fluid. This extension provides further ViewHelpers for TYPO3 specifics like link building.
+ext:fluid. This extension provides further ViewHelpers for TYPO3 specifics like link building.
 
-Fluid itself provides a basic **syntax**, this syntax is explained at
+Fluid itself provides a basic **syntax**, which is explained at
 https://github.com/TYPO3/Fluid/blob/master/doc/FLUID_SYNTAX.md .
 This syntax can be extended, see
 https://github.com/TYPO3/Fluid/blob/master/doc/FLUID_EXPRESSIONS.md .
 
 Also Fluid has different levels of **templates**. There is always a *Template*, which can
 contain different *Sections*. Also the *Template* can inherit a *Layout*.
 For easier re-use *Partials* can be created and rendered within *Layouts* and *Templates*.
-For further information on files check out
+For further information on the structure and usage of Fluid check out
 https://github.com/TYPO3/Fluid/blob/master/doc/FLUID_STRUCTURE.md .
 
 In TYPO3's extensions the default lookup paths are:
@@ -67,13 +68,13 @@ Layouts
 Partials
    Resources/Private/Partials
 
-But these can be configured through TypoScript, via
+But these can be configured through TypoScript via
 :ref:`t3tsref:cobj-fluidtemplate-properties-templaterootpaths`,
 :ref:`t3tsref:cobj-fluidtemplate-properties-layoutrootpaths` and
 :ref:`t3tsref:cobj-fluidtemplate-properties-partialrootpaths`.
 
-To further extend Fluid, there are **ViewHelpers**. These are basically custom
-HTML-Tags which contain PHP Logic.
+To further extend Fluid, there are **ViewHelpers**. These are custom HTML-Tags which
+contain PHP Logic.
 To understand what they are and how to use them, check out
 https://github.com/TYPO3/Fluid/blob/master/doc/FLUID_VIEWHELPERS.md .
 If you want to write your own ViewHelpers take a look at