foofvzxc

README.md

@@ -12,7 +12,7 @@ When you access the GitLab server over ssh then GitLab Shell will:
 1. It will execute the pre-receive hooks (called Git Hooks in GitLab Enterprise Edition)
 1. It will execute the action you requested
 1. Process the GitLab post-receive actions
-1. Process any custom post-receive actions
+1. Process any custom post-receive actions bxcvbxcvbv
 If you access a GitLab server over http(s) what happens depends on if you pull from or push to the git repository.
 If you pull from git repositories over http(s) the GitLab Rails app will completely handle the authentication and execution.
@@ -21,7 +21,7 @@ If you push to git repositories over http(s) the GitLab Rails app will not handl
 1. Call the GitLab Rails API to check if you are authorized
 1. It will execute the pre-receive hooks (called Git Hooks in GitLab Enterprise Edition)
 1. It will excute the action you requested
-1. Process the GitLab post-receive actionsdasfasdfasd
+1. Process the GitLab post-receive actions
 1. Process any custom post-receive actions
 Maybe you wonder why in the case of git push over http(s) the Rails app doesn't handle authentication before delegating to GitLab Shell.