Update Index.rst

Documentation/Concepts/Backend/MediaModule/Index.rst

@@ -72,7 +72,7 @@ For usage in PHP there is an API: :ref:`Working with files, folders and file
 references <t3coreapi:fal-using-fal-examples-file-folder>`
 
 ..  note::
-    Never link to a file in the fileadmin from CSS or or JavaScript. Such files
+    Never link to a file in the fileadmin from CSS or JavaScript. Such files
     like logos, icons, background images, etc. should be stored as
     :ref:`Assets in extensions and site packages <assets>`.
 
@@ -81,7 +81,7 @@ references <t3coreapi:fal-using-fal-examples-file-folder>`
 File metadata
 ==============
 
-A number of metadata fields for media uploaded in the :guilabel:`Media` module is
+A number of metadata fields for media uploaded in the :guilabel:`Media` module are
 available out-of-the-box. Additional metadata fields are available if the
 system extension :composer:`typo3/cms-filemetadata` is installed.
 

Documentation/Concepts/Backend/RecordsModule/Index.rst

@@ -31,7 +31,7 @@ Display of database records in the Records module
 
 How a database record type is displayed in the :guilabel:`Content > Records` module is determined by
 :ref:`tca` and can be further configured by TSconfig. While TCA is always loaded
-globally Tsconfig can be included on a per-site or per-page level.
+globally TSconfig can be included on a per-site or per-page level.
 
 ..  todo: Link tsconfig once article exists in concepts.
 
@@ -90,5 +90,5 @@ set globally in the :ref:`tca` by setting a custom default value in TSconfig
     # Do not hide newly created pages by default
     TCAdefaults.pages.hidden = 0
 
-    # Set the author of a news to "Anonymous"
+    # Set the author of a news record to "Anonymous"
     TCAdefaults.tx_news_domain_model_news.author = Anonymous

Documentation/Concepts/Backend/SiteManagement/PageTSconfig.rst

@@ -22,8 +22,8 @@ called :file:`EXT:my_extension/Configuration/page.tsconfig` or inserted or
 included in the record of a page in the page properties. Doing so is still
 possible for backward compatibility reasons.
 
-If you included the Page TSconfig via a site set or globally it
-not displayed in the overview submodule.
+If you included the Page TSconfig via a site set or globally, then it
+will not be displayed in the overview submodule.
 
 This does not mean it is not being loaded.
 
@@ -42,7 +42,7 @@ Included page TSconfig
 This module works much like :ref:`site-management-typoscript-included`, however
 the sources from which TSconfig is being loaded are different.
 
-In this Guide we assume that you load page TSconfig via the the site set of your
+In this Guide we assume that you load page TSconfig via the site set of your
 site package. The TSconfig Reference gives you an overview of all possible
 strategies to set page TSconfig:
 :ref:`Setting page TSconfig <t3tsref:setting-page-tsconfig>`.

Documentation/Concepts/Backend/SiteManagement/TypoScript.rst

@@ -12,14 +12,14 @@ that you provided via your site as described in
 or via your site set as described in the Site Package Tutorial, chapter
 :ref:`The TypoScript-only version <t3sitepackage:make-typoscript-available>`.
 
-Before TYPO3 v13 TypoScript was managed via database records, called "TypoScript
-records". It is still possible doing this and you will see it in older examples
-or installations that have been updated and not refactored. This module can
+Before TYPO3 v13, TypoScript was managed via database records called "TypoScript
+records". It is still possible to do this, and you will see it in older examples
+or installations that have been updated and not yet refactored. This module can
 also be used to manage TypoScript records. Its usage is described in
 TypoScript Reference, chapter
 :ref:`TypoScript backend module <t3tsref:typoscript-syntax-typoscript-templates-structure>`.
 
-In the context of this guide we concentrate on the new way of providing TypoScript
+In the context of this guide, we concentrate on the new way of providing TypoScript
 via the site only.
 
 The TypoScript module consists of the following submodules. You can switch them
@@ -39,20 +39,20 @@ TypoScript Overview
 ===================
 
 Global overview of all pages with active TypoScript definitions (TypoScript
-records and site sets). Useful if you have more then one site or more then one
+records and site sets). Useful if you have more than one site or more than one
 TypoScript record in one site.
 
 ..  _site-management-typoscript-constant-editor:
 
 Constant Editor
 ===============
 
-Before site settings were introduced with TYPO3 13, TypoScript constants where
+Before site settings were introduced with TYPO3 13, TypoScript constants were
 used to define values once and reuse them across TypoScript definitions.
 
-Constants can still be used for backward compatibility reasons but the
-Constant Editor is not available if you are using site sets. Other
-then site settings, TypoScript constants are only available within TypoScript.
+Constants can still be used for backward compatibility reasons, but the
+Constant Editor is not available, if you are using site sets. Unlike
+site settings, TypoScript constants are only available within TypoScript.
 
 It is therefore recommended to always use site settings.
 
@@ -61,9 +61,9 @@ It is therefore recommended to always use site settings.
 Edit TypoScript record
 ======================
 
-Only available if TypoScript records are being used. Can be used to edit those
-records. As we manage TypoScript within the site in this Guide it is out of
-scope of this Guide. Its usage is described in the TypoScript reference,
+Only available if TypoScript records are being used. This module can be used to
+edit those records. Since this guide focuses on managing TypoScript within the site, 
+this module is out of scope. Its usage is described in the TypoScript reference,
 chapter :ref:`Submodule "Edit TypoScript Record" <t3tsref:typoscript_module_edit>`.
 
 ..  _site-management-typoscript-active:
@@ -72,29 +72,29 @@ Active TypoScript
 =================
 
 This module can be used to debug the active TypoScript. During loading and
-pre compiling TypoScript configuration can override or unset definitions made in
+pre-compiling, TypoScript configuration can override or unset definitions made in
 another file.
 
 How exactly this happens depends on things like dependencies between the used
 site sets.
 
-For example if a site set in your site package configures:
+For example, if a site set in your site package configures:
 
 ..  code-block:: typoscript
     :caption: EXT:site_package/Configuration/Sets/SitePackage/setup.typoscript
 
     page.20 = TEXT
     page.20.value = Apple
 
-And the set of another extensions configures:
+And the set of another extension configures:
 
 ..  code-block:: typoscript
     :caption: EXT:some_extension/Configuration/Sets/BananaSet/setup.typoscript
 
     page.20 = TEXT
     page.20.value = Banana
 
-It depends on how these sets are loaded weather the `page.20.value` ends up
+It depends on how these sets are loaded whether the `page.20.value` ends up
 being set to "Banana" or "Apple".
 
 If the site set of our site package **depends** on the Banana set, the