1 files changed, 5 insertions, 5 deletions

diff --git a/doc/administration/restart_gitlab.md b/doc/administration/restart_gitlab.md
index f4cc98ca145..5f7f08f4ecf 100644
--- a/doc/administration/restart_gitlab.md
+++ b/doc/administration/restart_gitlab.md
@@ -27,7 +27,7 @@ GitLab Rails application (Puma) as well as the other components, like:
 
 ### Omnibus GitLab restart
 
-There may be times in the documentation where you will be asked to _restart_
+There may be times in the documentation where you are asked to _restart_
 GitLab. In that case, you need to run the following command:
 
 ```shell
@@ -73,7 +73,7 @@ As a last resort, you can try to
 
 ### Omnibus GitLab reconfigure
 
-There may be times in the documentation where you will be asked to _reconfigure_
+There may be times in the documentation where you are asked to _reconfigure_
 GitLab. Remember that this method applies only for the Omnibus packages.
 
 Reconfigure Omnibus GitLab with:
@@ -86,15 +86,15 @@ Reconfiguring GitLab should occur in the event that something in its
 configuration (`/etc/gitlab/gitlab.rb`) has changed.
 
 When you run this command, [Chef](https://www.chef.io/products/chef-infra/), the underlying configuration management
-application that powers Omnibus GitLab, will make sure that all things like directories,
+application that powers Omnibus GitLab, makes sure that all things like directories,
 permissions, and services are in place and in the same shape that they were
 initially shipped.
 
-It will also restart GitLab components where needed, if any of their
+It also restarts GitLab components where needed, if any of their
 configuration files have changed.
 
 If you manually edit any files in `/var/opt/gitlab` that are managed by Chef,
-running reconfigure will revert the changes AND restart the services that
+running reconfigure reverts the changes AND restarts the services that
 depend on those files.
 
 ## Installations from source