diff --git a/Documentation/Concepts/Backend/MediaModule/Index.rst b/Documentation/Concepts/Backend/MediaModule/Index.rst index b89f5e1a..df6a478c 100644 --- a/Documentation/Concepts/Backend/MediaModule/Index.rst +++ b/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 ` .. 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 `. @@ -81,7 +81,7 @@ references ` 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. diff --git a/Documentation/Concepts/Backend/RecordsModule/Index.rst b/Documentation/Concepts/Backend/RecordsModule/Index.rst index 81789aa6..cf73f9fd 100644 --- a/Documentation/Concepts/Backend/RecordsModule/Index.rst +++ b/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 diff --git a/Documentation/Concepts/Backend/SiteManagement/PageTSconfig.rst b/Documentation/Concepts/Backend/SiteManagement/PageTSconfig.rst index f38b82b5..e2dad65c 100644 --- a/Documentation/Concepts/Backend/SiteManagement/PageTSconfig.rst +++ b/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 `. diff --git a/Documentation/Concepts/Backend/SiteManagement/TypoScript.rst b/Documentation/Concepts/Backend/SiteManagement/TypoScript.rst index 8ac141cf..b0aafcbd 100644 --- a/Documentation/Concepts/Backend/SiteManagement/TypoScript.rst +++ b/Documentation/Concepts/Backend/SiteManagement/TypoScript.rst @@ -12,15 +12,15 @@ 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 `. -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 -also be used to manage TypoScript records. Its usage is described in -TypoScript Reference, chapter +Before TYPO3 v13, TypoScript was set in database records called "TypoScript +records". It is still possible to do this, and you will see it in older documentation +and installations that have been updated but not yet refactored. The TypoScript +backend module can be used to manage these TypoScript records, see +the TypoScript Reference in chapter :ref:`TypoScript backend module `. -In the context of this guide we concentrate on the new way of providing TypoScript -via the site only. +In the context of this guide, we concentrate on the new way of providing TypoScript +via the site. The TypoScript module consists of the following submodules. You can switch them in the docheader: @@ -39,7 +39,7 @@ 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: @@ -47,12 +47,12 @@ TypoScript record in one site. Constant Editor =============== -Before site settings were introduced with TYPO3 13, TypoScript constants where -used to define values once and reuse them across TypoScript definitions. +Before site settings were introduced in TYPO3 13, TypoScript constants were +values that were defined in one place that could then be reused 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 in TypoScript. It is therefore recommended to always use site settings. @@ -61,9 +61,10 @@ 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. For further information about TypoScript records, +see the TypoScript reference, chapter :ref:`Submodule "Edit TypoScript Record" `. .. _site-management-typoscript-active: @@ -71,14 +72,14 @@ chapter :ref:`Submodule "Edit TypoScript Record"