Add latest changes from gitlab-org/gitlab@master

2 files changed, 5 insertions, 5 deletions

diff --git a/doc/development/experiment_guide/index.md b/doc/development/experiment_guide/index.md
index c8c396d2d60..163cd009c51 100644
--- a/doc/development/experiment_guide/index.md
+++ b/doc/development/experiment_guide/index.md
@@ -27,7 +27,7 @@ sometimes referred to as GLEX, to run our experiments. The gem exists in a separ
 so it can be shared across any GitLab property that uses Ruby. You should feel comfortable reading
 the documentation on that project if you want to dig into more advanced topics or open issues. Be
 aware that the documentation there reflects what's in the main branch and may not be the same as
-the version being used within GitLab.
+the version being used in GitLab.
 
 ## Glossary of terms
 
@@ -43,7 +43,7 @@ when communicating about experiments:
 
 ## Implementing an experiment
 
-[`GLEX`](https://gitlab.com/gitlab-org/ruby/gems/gitlab-experiment) - or `Gitlab::Experiment`, the `gitlab-experiment` gem - is the preferred option for implementing an experiment in GitLab.
+[GLEX](https://gitlab.com/gitlab-org/ruby/gems/gitlab-experiment) - or `Gitlab::Experiment`, the `gitlab-experiment` gem - is the preferred option for implementing an experiment in GitLab.
 
 For more information, see [Implementing an A/B/n experiment using GLEX](implementing_experiments.md).
 
diff --git a/doc/development/experiment_guide/testing_experiments.md b/doc/development/experiment_guide/testing_experiments.md
index 3593111122d..a73896c8436 100644
--- a/doc/development/experiment_guide/testing_experiments.md
+++ b/doc/development/experiment_guide/testing_experiments.md
@@ -8,7 +8,7 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 
 ## Testing experiments with RSpec
 
-In the course of working with experiments, you'll probably want to use the RSpec
+In the course of working with experiments, you might want to use the RSpec
 tooling that's built in. This happens automatically for files in `spec/experiments`, but
 for other files and specs you want to include it in, you can specify the `:experiment` type:
 
@@ -84,7 +84,7 @@ expect(subject).to track(:my_event)
 subject.track(:my_event)
 ```
 
-You can use the `on_next_instance` chain method to specify that it will happen
+You can use the `on_next_instance` chain method to specify that it happens
 on the next instance of the experiment. This helps you if you're calling
 `experiment(:example).track` downstream:
 
@@ -127,7 +127,7 @@ describe('when my_experiment is enabled', () => {
 ```
 
 NOTE:
-This method of stubbing in Jest specs will not automatically un-stub itself at the end of the test. We merge our stubbed experiment in with all the other global data in `window.gl`. If you need to remove the stubbed experiments after your test or ensure a clean global object before your test, you'll need to manage the global object directly yourself:
+This method of stubbing in Jest specs does not automatically un-stub itself at the end of the test. We merge our stubbed experiment in with all the other global data in `window.gl`. If you must remove the stubbed experiments after your test or ensure a clean global object before your test, you must manage the global object directly yourself:
 
 ```javascript
 describe('tests that care about global state', () => {