diff options
| author | Pascal Borreli <pascal@borreli.com> | 2018-04-27 11:50:05 +0300 |
|---|---|---|
| committer | Rémy Coutable <remy@rymai.me> | 2018-04-27 11:50:05 +0300 |
| commit | 12e3eff462077008143146181c81f77204d1a8a9 (patch) | |
| tree | 3a7c1cf7ae9004a27df9d1c3d942a138185a3ee2 /doc/ssh | |
| parent | 740f0bb126a4e7da94d9d0181d2023b14113c93e (diff) | |
Fixed typos
Diffstat (limited to 'doc/ssh')
| -rw-r--r-- | doc/ssh/README.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ssh/README.md b/doc/ssh/README.md index aa14a39e4c9..b71e9bf3000 100644 --- a/doc/ssh/README.md +++ b/doc/ssh/README.md @@ -196,7 +196,7 @@ This is really useful for integrating repositories to secured, shared Continuous Integration (CI) services or other shared services. GitLab administrators can set up the Global Shared Deploy key in GitLab and add the private key to any shared systems. Individual repositories opt into -exposing their repsitory using these keys when a project masters (or higher) +exposing their repository using these keys when a project masters (or higher) authorizes a Global Shared Deploy key to be used with their project. Global Shared Keys can provide greater security compared to Per-Project Deploy @@ -224,7 +224,7 @@ if there is at least one Global Deploy Key configured. CAUTION: **Warning:** Defining Global Deploy Keys does not expose any given repository via -the key until that respository adds the Global Deploy Key to their project. +the key until that repository adds the Global Deploy Key to their project. In this way the Global Deploy Keys enable access by other systems, but do not implicitly give any access just by setting them up. |