summaryrefslogtreecommitdiff
path: root/doc/development/internal_api.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2019-11-27 06:06:40 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2019-11-27 06:06:40 +0000
commit688e33953d34ab8cd348d02ce79d8fdfe5353a03 (patch)
treeee102361fc8a5bf5b2f4b05ca79ccef27b5c3102 /doc/development/internal_api.md
parent91f027ede40879af0bce406f2872e8d35c01e334 (diff)
downloadgitlab-ce-688e33953d34ab8cd348d02ce79d8fdfe5353a03.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/internal_api.md')
-rw-r--r--doc/development/internal_api.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/development/internal_api.md b/doc/development/internal_api.md
index b08112aacb2..18d88c37147 100644
--- a/doc/development/internal_api.md
+++ b/doc/development/internal_api.md
@@ -4,8 +4,8 @@ The internal API is used by different GitLab components, it can not be
used by other consumers. This documentation is intended for people
working on the GitLab codebase.
-This documentation does not yet include the internal api used by
-GitLab pages.
+This documentation does not yet include the internal API used by
+GitLab Pages.
## Authentication
@@ -19,7 +19,7 @@ file, and include the token Base64 encoded in a `secret_token` param
or in the `Gitlab-Shared-Secret` header.
NOTE: **Note:**
-The internal api used by GitLab pages uses a different kind of
+The internal API used by GitLab Pages uses a different kind of
authentication.
## Git Authentication
@@ -119,7 +119,7 @@ curl --request POST --header "Gitlab-Shared-Secret: <Base64 encoded token>" --da
## Authorized Keys Check
This endpoint is called by the GitLab-shell authorized keys
-check. Which is called by OpenSSH for [fast ssh key
+check. Which is called by OpenSSH for [fast SSH key
lookup](../administration/operations/fast_ssh_key_lookup.md).
| Attribute | Type | Required | Description |
@@ -292,7 +292,7 @@ Example response:
## PostReceive
Called from Gitaly after a receiving a push. This triggers the
-`PostReceive`-worker in sidekiq, processes the passed push options and
+`PostReceive`-worker in Sidekiq, processes the passed push options and
builds the response including messages that need to be displayed to
the user.