diff --git a/docs/deployment-methods.md b/docs/deployment-methods.md
index 82a5847..55e50b2 100644
--- a/docs/deployment-methods.md
+++ b/docs/deployment-methods.md
@@ -19,7 +19,7 @@ Zip the content of your project into a tarball (`.tar`), go to your Captain web
 This method is perhaps the most convinient one. This method automatically triggers a build when you push your repo to a specific branch (like `master` or `staging` or etc). To setup this, go to your apps settings and enter the repo information:
 - github/bitbucket username(email address): This is username that will be used when Captain downloads the repo.
 - github/bitbucket password: You can enter any non-empty text, like `123456`, for public projects.
-- repo: This is the main HTTPS address of repo, in case of github, it is in `github.com/someone/something` format.
+- repo: This is the main HTTPS address of repo, in case of github, it is in `github.com/someone/something` format. Make sure it does NOT include `https://` prefix and `.git` suffix.
 - branch: The branch you want to be tracked, for example `master` or `production`...
 
 After you enter this information, save your configuration. And go to your apps page again. Now, you'll see a new field call webhook. Simply copy this webhook to your github/bitbucket repo. Captain listens to `POST` requests on this link and triggers a build.