Exchange occurrences of e.g. with for example

doc/development/cicd/index.md

@@ -157,7 +157,7 @@ On top of that, we have the following types of jobs:
 
 - `Ci::Build` ... The job to be executed by runners.
 - `Ci::Bridge` ... The job to trigger a downstream pipeline.
-- `GenericCommitStatus` ... The job to be executed in an external CI/CD system e.g. Jenkins.
+- `GenericCommitStatus` ... The job to be executed in an external CI/CD system, for example Jenkins.
 
 When you use the "Job" terminology in codebase, readers would
 assume that the class/object is any type of above.

doc/development/contributing/issue_workflow.md

@@ -151,7 +151,7 @@ From the handbook's
 page:
 
 > Categories are high-level capabilities that may be a standalone product at
-another company. e.g. Portfolio Management.
+another company, such as Portfolio Management, for example.
 
 It's highly recommended to add a category label, as it's used by our triage
 automation to
@@ -182,7 +182,7 @@ From the handbook's
 [Product stages, groups, and categories](https://about.gitlab.com/handbook/product/categories/#hierarchy)
 page:
 
-> Features: Small, discrete functionalities. e.g. Issue weights. Some common
+> Features: Small, discrete functionalities, for example Issue weights. Some common
 features are listed within parentheses to facilitate finding responsible PMs by keyword.
 
 It's highly recommended to add a feature label if no category label applies, as

doc/development/distributed_tracing.md

@@ -57,7 +57,7 @@ on non-Go GitLab subsystems.
 ## Enabling distributed tracing
 
 GitLab uses the `GITLAB_TRACING` environment variable to configure distributed tracing. The same
-configuration is used for all components (e.g., Workhorse, Rails, etc).
+configuration is used for all components (for example, Workhorse, Rails, etc).
 
 When `GITLAB_TRACING` is not set, the application isn't instrumented, meaning that there is
 no overhead at all.