diff --git a/doc/user/application_security/dependency_scanning/analyzers.md b/doc/user/application_security/dependency_scanning/analyzers.md
index 8559d5af02ee16505715d07463d78a0e85638429..f0d522f1e6dea66b70e62442be4c9df63f915050 100644
--- a/doc/user/application_security/dependency_scanning/analyzers.md
+++ b/doc/user/application_security/dependency_scanning/analyzers.md
@@ -118,12 +118,12 @@ The following table lists the data available for each official analyzer.
 | File                                  | ✓                  | ⚠                  | ✓                  |
 | Start line                            | 𐄂                  | 𐄂                  | 𐄂                  |
 | End line                              | 𐄂                  | 𐄂                  | 𐄂                  |
-| External ID (e.g., CVE)               | ✓                  | ✓                  | ⚠                  |
+| External ID (for example, CVE)        | ✓                  | ✓                  | ⚠                  |
 | URLs                                  | ✓                  | ✓                  | ✓                  |
 | Internal doc/explanation              | ✓                  | 𐄂                  | 𐄂                  |
 | Solution                              | ✓                  | ✓                  | 𐄂                  |
 | Confidence                            | 𐄂                  | 𐄂                  | 𐄂                  |
-| Affected item (e.g. class or package) | ✓                  | ✓                  | ✓                  |
+| Affected item (for example, class or package) | ✓                  | ✓                  | ✓                  |
 | Source code extract                   | 𐄂                  | 𐄂                  | 𐄂                  |
 | Internal ID                           | ✓                  | 𐄂                  | 𐄂                  |
 | Date                                  | ✓                  | 𐄂                  | 𐄂                  |
@@ -134,4 +134,4 @@ The following table lists the data available for each official analyzer.
 - 𐄂 => we don't have that data, or it would need to develop specific or inefficient/unreliable logic to obtain it.
 
 The values provided by these tools are heterogeneous, so they are sometimes
-normalized into common values (e.g., `severity`, `confidence`, etc).
+normalized into common values (for example, `severity`, `confidence`, etc).
diff --git a/doc/user/compliance/license_compliance/index.md b/doc/user/compliance/license_compliance/index.md
index b9e2a26197f445859a94ca71cc241941694db0ef..7b8c2d5cff8b6cecf12f39f524943a0c2fb0ca8b 100644
--- a/doc/user/compliance/license_compliance/index.md
+++ b/doc/user/compliance/license_compliance/index.md
@@ -176,7 +176,7 @@ For that, a `SETUP_CMD` CI/CD variable can be passed to the container,
 with the required commands to run before the license detection.
 
 If present, this variable overrides the setup step necessary to install all the packages
-of your application (e.g.: for a project with a `Gemfile`, the setup step could be
+of your application (for example: for a project with a `Gemfile`, the setup step could be
 `bundle install`).
 
 For example:
diff --git a/doc/user/project/insights/index.md b/doc/user/project/insights/index.md
index 436df07d67318a836a31b5a20128d0f77692e347..957290c5f205cd88bb3b9971ebca42730fd95a68 100644
--- a/doc/user/project/insights/index.md
+++ b/doc/user/project/insights/index.md
@@ -149,7 +149,7 @@ Supported values are:
 | Name  | Example |
 | ----- | ------- |
 | `bar` | ![Insights example bar chart](img/insights_example_bar_chart.png) |
-| `bar` (time series, i.e. when `group_by` is used) | ![Insights example bar time series chart](img/insights_example_bar_time_series_chart.png) |
+| `bar` (time series, that is when `group_by` is used) | ![Insights example bar time series chart](img/insights_example_bar_time_series_chart.png) |
 | `line` | ![Insights example stacked bar chart](img/insights_example_line_chart.png) |
 | `stacked-bar` | ![Insights example stacked bar chart](img/insights_example_stacked_bar_chart.png) |
 
diff --git a/doc/user/search/advanced_search.md b/doc/user/search/advanced_search.md
index 5888b660c9b5d79284769ef0e751afbf755401b6..20881a6bdb311f1cf3f322d9dd4d131625b286ae 100644
--- a/doc/user/search/advanced_search.md
+++ b/doc/user/search/advanced_search.md
@@ -66,7 +66,7 @@ you matching code from each project you have access to.
 Full details can be found in the [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/5.3/query-dsl-simple-query-string-query.html#_simple_query_string_syntax), but
 here's a quick guide:
 
-- Searches look for all the words in a query, in any order - e.g.: searching
+- Searches look for all the words in a query, in any order - for example: searching
   issues for [`display bug`](https://gitlab.com/search?snippets=&scope=issues&repository_ref=&search=display+bug&group_id=9970&project_id=278964) and [`bug display`](https://gitlab.com/search?snippets=&scope=issues&repository_ref=&search=bug+Display&group_id=9970&project_id=278964) will return the same results.
 - To find the exact phrase (stemming still applies), use double quotes: [`"display bug"`](https://gitlab.com/search?snippets=&scope=issues&repository_ref=&search=%22display+bug%22&group_id=9970&project_id=278964)
 - To find bugs not mentioning display, use `-`: [`bug -display`](https://gitlab.com/search?snippets=&scope=issues&repository_ref=&search=bug+-display&group_id=9970&project_id=278964)