summaryrefslogtreecommitdiff
path: root/doc/administration/gitaly
diff options
context:
space:
mode:
authorBen Bodenmiller <bbodenmiller@hotmail.com>2019-07-03 10:55:15 +0000
committerAchilleas Pipinellis <axil@gitlab.com>2019-07-03 10:55:15 +0000
commit8f9288968ec564226a183d9a0b58f3cf35678801 (patch)
tree8628ddcc50a896af479fffb8b6d9c2495ee64f5e /doc/administration/gitaly
parent9b06890d1d6901b840fb321c9b99264c2e8813f7 (diff)
downloadgitlab-ce-8f9288968ec564226a183d9a0b58f3cf35678801.tar.gz
Gitlab -> GitLab
Diffstat (limited to 'doc/administration/gitaly')
-rw-r--r--doc/administration/gitaly/index.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/administration/gitaly/index.md b/doc/administration/gitaly/index.md
index 0bffe2f7472..a3cbc4272f0 100644
--- a/doc/administration/gitaly/index.md
+++ b/doc/administration/gitaly/index.md
@@ -267,7 +267,7 @@ repository from your GitLab server over HTTP.
Gitaly supports TLS encryption. To be able to communicate
with a Gitaly instance that listens for secure connections you will need to use `tls://` url
-scheme in the `gitaly_address` of the corresponding storage entry in the gitlab configuration.
+scheme in the `gitaly_address` of the corresponding storage entry in the GitLab configuration.
The admin needs to bring their own certificate as we do not provide that automatically.
The certificate to be used needs to be installed on all Gitaly nodes and on all client nodes that communicate with it following procedures described in [GitLab custom certificate configuration](https://docs.gitlab.com/omnibus/settings/ssl.html#install-custom-public-certificates).