Merge branch 'docs-distro-etc-rem' into 'master'

Remove etc from Distribution docs

See merge request gitlab-org/gitlab!72543

doc/administration/package_information/deprecation_policy.md

 ---
 stage: Enablement
 group: Distribution
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
 # Deprecation policy **(FREE SELF)**
@@ -35,9 +35,11 @@ This section lists steps necessary for deprecating and removing configuration.
 
 We can differentiate two different types of configuration:
 
-- Sensitive: Configuration that can cause major service outage ( Data integrity,
-  installation integrity, preventing users from reaching the installation, etc.)
-- Regular: Configuration that can make a feature unavailable but still makes the installation useable ( Change in default project/group settings, miscommunication with other components and similar )
+- Sensitive: Configuration that can cause major service outage (like data integrity,
+  installation integrity, or preventing users from reaching the installation)
+- Regular: Configuration that can make a feature unavailable but still makes the
+  installation useable (like a change in default project/group settings, or
+  miscommunication with other components)
 
 We also need to differentiate deprecation and removal procedure.
 

doc/install/aws/manual_install_aws.md

@@ -2,7 +2,6 @@
 stage: Enablement
 group: Distribution
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
-type: howto
 ---
 
 {::options parse_block_html="true" /}
@@ -410,7 +409,10 @@ persistence and is used to store session data, temporary cache information, and
 
 ## Setting up Bastion Hosts
 
-Since our GitLab instances will be in private subnets, we need a way to connect to these instances via SSH to make configuration changes, perform upgrades, etc. One way of doing this is via a [bastion host](https://en.wikipedia.org/wiki/Bastion_host), sometimes also referred to as a jump box.
+Because our GitLab instances are in private subnets, we need a way to connect
+to these instances with SSH for actions that include making configuration changes
+and performing upgrades. One way of doing this is by using a [bastion host](https://en.wikipedia.org/wiki/Bastion_host),
+sometimes also referred to as a jump box.
 
 NOTE:
 If you do not want to maintain bastion hosts, you can set up [AWS Systems Manager Session Manager](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html) for access to instances. This is beyond the scope of this document.

doc/install/docker.md

@@ -27,7 +27,7 @@ WARNING:
 Docker for Windows is not officially supported. There are known issues with volume
 permissions, and potentially other unknown issues. If you are trying to run on Docker
 for Windows, see the [getting help page](https://about.gitlab.com/get-help/) for links
-to community resources (IRC, forum, etc.) to seek help from other users.
+to community resources (such as IRC or forums) to seek help from other users.
 
 ## Prerequisites
 

doc/install/google_cloud_platform/index.md

@@ -3,7 +3,6 @@ stage: Enablement
 group: Distribution
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 description: 'Learn how to install a GitLab instance on Google Cloud Platform.'
-type: howto
 ---
 
 # Installing GitLab on Google Cloud Platform **(FREE SELF)**
@@ -126,8 +125,8 @@ Check the [Omnibus documentation](https://docs.gitlab.com/omnibus/settings/smtp.
 
 ## Further reading
 
-GitLab can be configured to authenticate with other OAuth providers, LDAP, SAML,
-Kerberos, etc. Here are some documents you might be interested in reading:
+GitLab can be configured to authenticate with other OAuth providers, like LDAP,
+SAML, and Kerberos. Here are some documents you might be interested in reading:
 
 - [Omnibus GitLab documentation](https://docs.gitlab.com/omnibus/)
 - [Integration documentation](../../integration/index.md)

doc/install/installation.md

@@ -2,7 +2,6 @@
 stage: Enablement
 group: Distribution
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
-type: howto
 ---
 
 # Installation from source **(FREE SELF)**
@@ -838,7 +837,9 @@ Validate your `gitlab` or `gitlab-ssl` NGINX configuration file with the followi
 sudo nginx -t
 ```
 
-You should receive `syntax is okay` and `test is successful` messages. If you receive errors check your `gitlab` or `gitlab-ssl` NGINX configuration file for typos, etc. as indicated in the error message given.
+You should receive `syntax is okay` and `test is successful` messages. If you
+receive error messages, check your `gitlab` or `gitlab-ssl` NGINX configuration
+file for typos, as indicated in the provided error message.
 
 Verify that the installed version is greater than 1.12.1:
 

doc/install/relative_url.md

@@ -2,7 +2,6 @@
 stage: Enablement
 group: Distribution
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
-type: reference
 ---
 
 # Install GitLab under a relative URL **(FREE SELF)**
@@ -37,11 +36,11 @@ After all the changes you need to recompile the assets and [restart GitLab](../a
 
 ## Relative URL requirements
 
-If you configure GitLab with a relative URL, the assets (JavaScript, CSS, fonts,
-images, etc.) will need to be recompiled, which is a task which consumes a lot
-of CPU and memory resources. To avoid out-of-memory errors, you should have at
-least 2GB of RAM available on your system, while we recommend 4GB RAM, and 4 or
-8 CPU cores.
+If you configure GitLab with a relative URL, the assets (including JavaScript,
+CSS, fonts, and images) must be recompiled, which can consume a lot of CPU and
+memory resources. To avoid out-of-memory errors, you should have at least 2 GB
+of RAM available on your computer, and we recommend 4 GB RAM, and four or eight
+CPU cores.
 
 See the [requirements](requirements.md) document for more information.
 

doc/integration/mattermost/index.md

 ---
 stage: Enablement
 group: Distribution
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
 # GitLab Mattermost
@@ -428,7 +428,7 @@ mattermost['env'] = {
 
 Refer to the [Mattermost Configuration Settings
 documentation](https://docs.mattermost.com/administration/config-settings.html)
-for details about categories, configuration values, etc.
+for details about categories and configuration values.
 
 There are a few exceptions to this rule: