summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPatOnTheBack <pat@softwaresolutions.ltd>2019-06-04 20:23:11 +0000
committerPatOnTheBack <pat@softwaresolutions.ltd>2019-06-04 20:23:11 +0000
commite5ed663e7c0e5282abaa58f0bce4470aab6c3057 (patch)
tree764262e7200ebc03d52296a830847b9f42b10159
parent632427bcc24403be21df5afe8e6bae9cf41c8bc7 (diff)
downloadgitlab-ce-e5ed663e7c0e5282abaa58f0bce4470aab6c3057.tar.gz
Update code_quality.md to fix grammatical errors.
-rw-r--r--doc/user/project/merge_requests/code_quality.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/user/project/merge_requests/code_quality.md b/doc/user/project/merge_requests/code_quality.md
index e6811b5df5e..705ff333579 100644
--- a/doc/user/project/merge_requests/code_quality.md
+++ b/doc/user/project/merge_requests/code_quality.md
@@ -19,7 +19,7 @@ in the merge request widget area:
For instance, consider the following workflow:
-1. Your backend team member starts a new implementation for making certain feature in your app faster
+1. Your backend team member starts a new implementation for making a certain feature in your app faster
1. With Code Quality reports, they analyze how their implementation is impacting the code quality
1. The metrics show that their code degrade the quality in 10 points
1. You ask a co-worker to help them with this modification
@@ -63,7 +63,7 @@ Example:
NOTE: **Note:**
Although the Code Climate spec supports more properties, those are ignored by GitLab.
-For more information on how the Code Quality job should look like, check the
+For more information on what the Code Quality job should look like, check the
example on [analyzing a project's code quality](../../../ci/examples/code_quality.md).
GitLab then checks this report, compares the metrics between the source and target