diff options
| author | Dan Doran <dan@dorananddaughters.com> | 2018-07-07 22:30:47 +0000 |
|---|---|---|
| committer | Rémy Coutable <remy@rymai.me> | 2018-08-29 17:35:37 +0200 |
| commit | 191dad29679553b8dd128ae2b7b1ccd74c299e2a (patch) | |
| tree | 57c3ce354a0e10bc19d7550e20cfb01d34a71334 | |
| parent | e6128cdccf2dba17b72d19026fe72ba22713877e (diff) | |
| download | gitlab-ce-191dad29679553b8dd128ae2b7b1ccd74c299e2a.tar.gz | |
Fixed two typos and adjusted one instance of punctuation according to the grammar rule for appositive commas
Originally submitted at
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6419.
Signed-off-by: Rémy Coutable <remy@rymai.me>
| -rw-r--r-- | doc/topics/autodevops/quick_start_guide.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/topics/autodevops/quick_start_guide.md b/doc/topics/autodevops/quick_start_guide.md index 44b0cf758dc..7ca441a2f74 100644 --- a/doc/topics/autodevops/quick_start_guide.md +++ b/doc/topics/autodevops/quick_start_guide.md @@ -143,7 +143,7 @@ In the next section we'll break down the pipeline and explain what each job does By now you should see the pipeline running, but what is it running exactly? -To navigate inside the pipeline, click its status badge. (It's status should be "running"). +To navigate inside the pipeline, click its status badge. (Its status should be "running"). The pipeline is split into 4 stages, each running a couple of jobs.  @@ -194,7 +194,7 @@ applications. In the rightmost column for the production environment, you can ma - The first icon will open the URL of the application that is deployed in production. It's a very simple page, but the important part is that it works! -- The next icon with the small graph will take you to the metrics page where +- The next icon, with the small graph, will take you to the metrics page where Prometheus collects data about the Kubernetes cluster and how the application affects it (in terms of memory/CPU usage, latency, etc.). @@ -217,7 +217,7 @@ under **Settings > CI/CD > Variables**. ### Working with branches -Following the [GitLab flow](../../workflow/gitlab_flow.md#working-with-feature-branches) +Following the [GitLab flow](../../workflow/gitlab_flow.md#working-with-feature-branches), let's create a feature branch that will add some content to the application. Under your repository, navigate to the following file: `app/views/welcome/index.html.erb`. @@ -235,7 +235,7 @@ by clicking **Commit**.  Once you submit the merge request, you'll see the pipeline running. This will -run all the jobs as [described previously](#deploying-the-application), as well +run all the jobs as [described previously](#deploying-the-application), as well as a few more that run only on branches other than `master`.  @@ -278,7 +278,7 @@ and the application will be eventually deployed straight to production. After implementing this project, you should now have a solid understanding of the basics of Auto DevOps. We started from building and testing to deploying and monitoring an application -all within GitLab. Despite its automatic nature, Audo DevOps can also be configured +all within GitLab. Despite its automatic nature, Auto DevOps can also be configured and customized to fit your workflow. Here are some helpful resources for further reading: 1. [Auto DevOps](index.md) |