who can trigger build info added

Author: michal-at-travisci

user/travis-ci-vcs-proxy-get-started.md

@@ -45,7 +45,7 @@ When you do it for the first time, a Travis CI VCS Proxy page will pop-up with a
 5. Please select a Trial Plan or wait for us to assign special Beta Plan to your account and/or organization(s). In Travis CI each individual User account and each Organization entity must have a separate plans assigned.
 > *Please note:* If assigning a plan doesn't remove automatically the insufficient user license/lack of credits error message in your Travis CI Beta application screen, please refresh your browser window manually (Ctrl/Cmd + F5).
 
-6. Add a `.travis.yml` file to your repository to tell Travis CI what to do.
+6. Create a `.travis.yml` file to tell Travis CI what to do.
 
 The following example specifies a Ruby project built with Ruby 2.2 and the latest versions of JRuby.
 
@@ -62,7 +62,7 @@ The defaults for Ruby projects are a `bundle install` to [install dependencies](
 
 7. Add the `.travis.yml` file to repository, commit to the repository to trigger a Travis CI build:
 
-   > Travis only runs builds on the commits you push *after* you've added a `.travis.yml` file.
+   > Travis only runs builds on the commits you push *after* you've added a `.travis.yml` file. As of now, only commits performed by the TCI VCS Proxy users with correct P4/SVN credentials may trigger automatic builds in the Travis CI.
 
  **IMPORTANT**