Commit 95d1fc03 authored by John Feeney's avatar John Feeney

Fixed a typo (missing word) in documentation on Deploy Keys

parent 9b516b9c
...@@ -27,7 +27,7 @@ repository in automation, it's a simple solution. ...@@ -27,7 +27,7 @@ repository in automation, it's a simple solution.
A drawback is that your repository could become vulnerable if a remote machine is compromised A drawback is that your repository could become vulnerable if a remote machine is compromised
by a hacker. You should limit access to the remote machine before a deploy key is by a hacker. You should limit access to the remote machine before a deploy key is
enabled on your repository. A good rule to follow is to access only to trusted users, enabled on your repository. A good rule to follow is to provide access only to trusted users,
and make sure that the allowed users have [maintainer permissions or higher](../../permissions.md) and make sure that the allowed users have [maintainer permissions or higher](../../permissions.md)
in the GitLab project. in the GitLab project.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment