kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Improve English, thanks Robert

This commit is contained in:
Jacob Vosmaer 2016-04-13 11:15:36 +02:00
parent a0bede92ed
commit 7478335826
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/administration/repository_checks.md
View File

@ -4,7 +4,7 @@ _**Note:** This feature was [introduced][ce-3232] in GitLab 8.7_
---
Git has a built-in mechanism \[git fsck\]\[git-fsck\] to verify the
Git has a built-in mechanism, \[git fsck\]\[git-fsck\], to verify the
integrity of all data commited to a repository. GitLab administrators
can trigger such a check for a project via the project page under the
admin panel. The checks run asynchronously so it may take a few minutes
@ -12,7 +12,7 @@ before the check result is visible on the project admin page. If the
checks failed you can see their output on the admin log page under
'repocheck.log'.
## Periodical checks
## Periodic checks
GitLab periodically runs a repository check on all project repositories and
wiki repositories in order to detect data corruption problems. A
@ -35,7 +35,7 @@ in repocheck.log (in the admin panel or on disk; see
resolved the issue use the admin panel to trigger a new repository check on
the project. This will clear the 'check failed' state.
If for some reason the periodical repository check caused a lot of false
If for some reason the periodic repository check caused a lot of false
alarms you can choose to clear ALL repository check states from the
'Settings' page of the admin panel.