[TASK] Overhaul extension development site package introduction (#6259)

Releases: main, 13.4

Co-authored-by: Sarah McCarthy <sarahmccarthy123@yahoo.com>

Author: github-actions[bot]

Documentation/ExtensionArchitecture/SitePackage/Introduction.rst

@@ -12,12 +12,12 @@ Introduction into using site packages
 Site package benefits
 =====================
 
-Developing a website can be approached in different ways. Standard
-websites usually consist of HTML documents which contain text and reference
+Developing a website can be approached in different ways. A typical
+website consists of HTML documents containing text and references to
 image files, video files, styles, etc. Because it is an enterprise content
-management system, TYPO3 features a clean separation between design, content and
-functionality and allows developers/integrators to add simple or
-sophisticated functionality easily.
+management system, TYPO3 has a clean separation between design, content and
+functionality and allows developers/integrators to easily add simple or
+sophisticated functionality.
 
 ..  _site-package-encapsulation:
 
@@ -26,37 +26,37 @@ Encapsulation
 
 Using extensions is a powerful way to get the most out of TYPO3. Extensions
 can be installed, uninstalled and replaced. They can extend the core TYPO3
-system with further functions and features. An extension typically
+system with new functions and features. An extension typically
 consists of PHP files, and can also contain design templates (HTML,
 CSS, JavaScript files, etc.) and global configuration settings. The visual
 appearance of a website does not necessarily require any PHP code. However, the
 site package extension described in this tutorial contains exactly two PHP files
 (plus a handful of HTML/CSS and configuration files) and is an *extension* to
-TYPO3. The PHP code can be copied from this tutorial if the reader does not
+TYPO3. You can simply copy the PHP code in this tutorial if you do not
 have any programming knowledge.
 
 ..  _site-package-version-controll:
 
 Version control
 ---------------
 
-In building the site package as an extension, all relevant files are stored in
-one place and changes can easily be tracked in a version control system
+The advantage of a site package extension is that all files relevant to the website
+are stored in one place and can easily be tracked in a version control system
 such as Git. The site package approach is not the only way of creating TYPO3
-websites but it is flexible and professional and not overly complicated.
+websites but it is convenient and professional and not overly-complicated.
 
 ..  _site-package-di:
 
 Dependency management
 ---------------------
 
-TYPO3 extensions allow dependencies to other extensions and/or the TYPO3 version
-to be defined. This is called "Dependency Management" and makes deployment easy
-and fail-safe. Most TYPO3 sites are dependent on a number of extensions. Some
-examples are "News" or "Powermail". A site package extension which contains
+TYPO3 extensions can have specific dependencies set to other extensions and TYPO3
+versions. This is called "Dependency Management" and makes deployment easy
+and fail-safe. Most TYPO3 sites are dependent on extensions such as
+"News" and "Powermail". A site package extension which contains
 global configuration settings for these extensions will define the dependencies
 for you. When the site package extension is installed in an
-empty TYPO3 instance, all dependent extensions are automatically downloaded from
+empty TYPO3 instance, the dependent extensions are automatically downloaded from
 the `TYPO3 Extension Repository <https://extensions.typo3.org>`__ and installed.
 
 ..  _site-package-separation:
@@ -78,7 +78,7 @@ still not be stored in the userspace.
 Security
 --------
 
-Files in :file:`fileadmin/` are typically meant to be publicly accessible by
+Files in :file:`fileadmin/` are meant to be publicly accessible by
 convention. To avoid disclosing sensitive system information (see the
 :ref:`TYPO3 Security Guide <t3coreapi:security>` for further details),
 configuration files should not be stored in :file:`fileadmin/`.
@@ -89,10 +89,10 @@ Deployment
 ----------
 
 TYPO3 follows the *convention over configuration*
-paradigm. If files and directories in the site-package
+paradigm. If files and directories in the site package
 extension use the naming convention, they are loaded automatically as
 soon as the extension is installed/activated. This means the
-extension can be easily deployed using Composer.
+extension can easily be deployed with Composer.
 Deployment can be automated by system administrators.
 
 ..  _site-package-distributable: