anchor.diff:  
   Your application is then created, which might take some time. In the case of
   this template, MongoDB is created first, then the Node.js application is built
  -using the OpenShift source-to-image (S2I) builder.
  -
  -You can follow along on the Overview page of the web console to see the new resources being created, and watch the progress of the build and deployment. While the MongoDB pod is being created, its status is shown as pending. The MongoDB pod then starts up and displays its newly-assigned IP address.
  +using the {product-title} source-to-image (S2I) builder.
  +
  +You can follow along on the Overview page of the web console to see the new
  +resources being created, and watch the progress of the build and deployment.
  +While the MongoDB pod is being created, its status is shown as pending. The
  +MongoDB pod then starts up and displays its newly-assigned IP address.
   
   When the Node.js pod is running, the build is complete.
   
  
positive.code: ====
  +
  The secret ensures that only you and your repository can trigger the build.
  . Run the following command to display the webhook URLs associated with your `*BuildConfig*`:
  +
  ----
  $ oc describe buildConfig <name>
  ----
  +
  . Copy the webhook URL output by the above command. If the above command does not display any webhook URLs, then no webhook trigger is defined for that build configuration.
  . Navigate to your forked repository on GitHub, then click *Settings*.
  . Click *Webhooks & Services*.
  . Click btn:[Add webhook].
  
negative.code: 
  // end::forking[]
  
  [[developers-cli-creating-a-project]]
  == Creating a Project
  
  To create an application, you must create a new project and specify the location
  of the source. From there, {product-title} begins the build process and creates
  a new deployment.
  
  . Log into {product-title} from the CLI:
  +
  * With username and password:
  +
  