Clean up substitution warning 5

doc/development/fe_guide/storybook.md

@@ -33,7 +33,7 @@ Stories can be added for any Vue component in the `gitlab` repository.
 To add a story:
 
 1. Create a new `.stories.js` file in the same directory as the Vue component.
-   The file name should have the same prefix as the Vue component.
+   The filename should have the same prefix as the Vue component.
 
     ```txt
     vue_shared/

doc/development/snowplow/index.md

@@ -720,7 +720,7 @@ The [`StandardContext`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/g
 | `geo_longitude`            | **{dotted-circle}** | string    | An approximate longitude                                                                                                         |
 | `geo_region`               | **{dotted-circle}** | string    | Region of IP origin                                                                                                              |
 | `geo_region_name`          | **{dotted-circle}** | string    | Region of IP origin                                                                                                              |
-| `geo_timezone`             | **{dotted-circle}** | string    | Timezone of IP origin                                                                                                            |
+| `geo_timezone`             | **{dotted-circle}** | string    | Time zone of IP origin                                                                                                            |
 | `geo_zipcode`              | **{dotted-circle}** | string    | Zip (postal) code of IP origin                                                                                                   |
 | `ip_domain`                | **{dotted-circle}** | string    | Second level domain name associated with the visitor's IP address                                                                |
 | `ip_isp`                   | **{dotted-circle}** | string    | Visitor's ISP                                                                                                                    |
@@ -738,7 +738,7 @@ The [`StandardContext`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/g
 | `os_family`                | **{dotted-circle}** | string    | Operating system family                                                                                                          |
 | `os_manufacturer`          | **{dotted-circle}** | string    | Manufacturers of operating system                                                                                                |
 | `os_name`                  | **{dotted-circle}** | string    | Name of operating system                                                                                                         |
-| `os_timezone`              | **{dotted-circle}** | string    | Client operating system timezone                                                                                                 |
+| `os_timezone`              | **{dotted-circle}** | string    | Client operating system time zone                                                                                                 |
 | `page_referrer`            | **{dotted-circle}** | string    | Referrer URL                                                                                                                     |
 | `page_title`               | **{dotted-circle}** | string    | Page title                                                                                                                       |
 | `page_url`                 | **{dotted-circle}** | string    | Page URL                                                                                                                         |

doc/development/stage_group_dashboards.md

@@ -120,7 +120,7 @@ Inside a stage group dashboard, there are some notable components. Let's take th
 
 ![Default time filter](img/stage_group_dashboards_time_filter.png)
 
-- By default, all the times are in UTC timezone. [We use UTC when communicating in Engineering](https://about.gitlab.com/handbook/communication/#writing-style-guidelines).
+- By default, all the times are in UTC time zone. [We use UTC when communicating in Engineering](https://about.gitlab.com/handbook/communication/#writing-style-guidelines).
 - All metrics recorded in the GitLab production system have [1-year retention](https://gitlab.com/gitlab-cookbooks/gitlab-prometheus/-/blob/31526b03fef823e2f9b3cda7c75dcd28a12418a3/attributes/prometheus.rb#L40).
 - Alternatively, you can zoom in or filter the time range directly on a graph. See the [Grafana Time Range Controls](https://grafana.com/docs/grafana/latest/dashboards/time-range-controls/) documentation for more information.
 

doc/development/testing_guide/end_to_end/best_practices.md

@@ -333,11 +333,11 @@ after(:all) do
 end
 ```
 
-## Tag tests that require Administrator access
+## Tag tests that require the Administrator role
 
-We don't run tests that require Administrator access against our Production environments.
+We don't run tests that require the Administrator role against our Production environments.
 
-When you add a new test that requires Administrator access, apply the RSpec metadata `:requires_admin` so that the test will not be included in the test suites executed against Production and other environments on which we don't want to run those tests.
+When you add a new test that requires the Administrator role, apply the RSpec metadata `:requires_admin` so that the test will not be included in the test suites executed against Production and other environments on which we don't want to run those tests.
 
 When running tests locally or configuring a pipeline, the environment variable `QA_CAN_TEST_ADMIN_FEATURES` can be set to `false` to skip tests that have the `:requires_admin` tag.