Merge branch 'docs/clean-up-vale-latin-terms-276202' into 'master'

Fixes vale latin terms error by replacing instances of e.g

See merge request gitlab-org/gitlab!73852

doc/development/fe_guide/storybook.md

@@ -47,8 +47,9 @@ To add a story:
 1. Write the story as per the [official Storybook instructions](https://storybook.js.org/docs/vue/writing-stories/introduction/)
 
    Notes:
-   - Specify the `title` field of the story as the component's file path from the `javascripts/` directory,
-     e.g. if the component is located at `app/assets/javascripts/vue_shared/components/sidebar/todo_toggle/todo_button.vue`, specify the story `title` as `vue_shared/components/sidebar/todo_toggle/todo_button`. This will ensure the Storybook navigation maps closely to our internal directory structure.
+   - Specify the `title` field of the story as the component's file path from the `javascripts/` directory.
+
+     For example, if the component is located at `app/assets/javascripts/vue_shared/components/sidebar/todo_toggle/todo_button.vue`, specify the story `title` as `vue_shared/components/sidebar/todo_toggle/todo_button`. This will ensure the Storybook navigation maps closely to our internal directory structure.
 
 ## Mock backend APIs
 

doc/development/understanding_explain_plans.md

@@ -172,7 +172,7 @@ cost describing how expensive the entire node was. In general: the greater the
 values, the more expensive the node.
 
 When using `EXPLAIN ANALYZE`, these statistics will also include the actual time
-(in milliseconds) spent, and other runtime statistics (e.g. the actual number of
+(in milliseconds) spent, and other runtime statistics (for example, the actual number of
 produced rows):
 
 ```sql
@@ -555,7 +555,7 @@ There are two terms commonly used for databases: cardinality, and selectivity.
 Cardinality refers to the number of unique values in a particular column in a
 table.
 
-Selectivity is the number of unique values produced by an operation (e.g. an
+Selectivity is the number of unique values produced by an operation (for example, an
 index scan or filter), relative to the total number of rows. The higher the
 selectivity, the more likely PostgreSQL is able to use an index.
 
@@ -675,8 +675,8 @@ best avoided in most cases, such as:
 
 - Sequential scans on large tables
 - Filters that remove a lot of rows
-- Performing a certain step (e.g. an index scan) that requires _a lot_ of
-  buffers (e.g. more than 512 MB for GitLab.com).
+- Performing a certain step that requires _a lot_ of
+  buffers (for example, an index scan for GitLab.com that requires more than 512 MB).
 
 As a general guideline, aim for a query that: