anchor.diff:  
   ## <a id='tag'></a>Benefits of Specifying Tags
   
  -If you want your app container to be consistent after platform updates and code changes, specify a tag 
  -when you push your Docker image. 
  +If you want your app container to be consistent after platform updates and code changes, specify a tag
  +when you push your Docker image.
   Otherwise, the platform applies the <code>latest</code> tag without respecting changes to `PORT` or `ENTRYPOINT`.
   
   If you push your Docker image without specifying a tag, you must run `cf restage` for the changes to take effect.
   
   ## <a id='port_config'></a>Port Configuration
   
  -By default, apps listen for connections on the port specified in the 
  -[PORT](environment-variable.html#PORT) 
  +By default, apps listen for connections on the port specified in the
  +[PORT](environment-variable.html#PORT)
   environment variable for the app. Cloud Foundry allocates this value dynamically.
   
  -When configuring a Docker image for Cloud Foundry, you can control the exposed port and 
  -the corresponding value of `PORT` by specifying the 
  -[EXPOSE](https://docs.docker.com/engine/reference/builder/#expose) directive in the image Dockerfile. 
  -If you specify the `EXPOSE` directive, then the corresponding app pushed to Cloud Foundry listens on that 
  +When configuring a Docker image for Cloud Foundry, you can control the exposed port and
  +the corresponding value of `PORT` by specifying the
  +[EXPOSE](https://docs.docker.com/engine/reference/builder/#expose) directive in the image Dockerfile.
  +If you specify the `EXPOSE` directive, then the corresponding app pushed to Cloud Foundry listens on that
   exposed port. For example, if you set `EXPOSE` to `7070`, then the app listens for connections on port 7070.
   
   If you do not specify a port in the `EXPOSE` directive, then the app listens on the value of the `PORT`
   environment variable as determined by Cloud Foundry.
  - 
  -If you set the `PORT` environment variable via an `ENV` directive in a Dockerfile, Cloud Foundry overrides 
  +
  +If you set the `PORT` environment variable via an `ENV` directive in a Dockerfile, Cloud Foundry overrides
   the value with the system-determined value.
   
  -Cloud Foundry supports only one exposed port on the image. 
  +Cloud Foundry supports only one exposed port on the image.
   
   ## <a id='start_command'></a>Start Command
   
  
positive.code: 
  ###<a id='cf-ssh'></a>Requirement for cf ssh Support
  
  If you want to log in to your app container using the <code>cf ssh</code> command, you must make a shell such as <code>sh</code> or <code>bash</code> available in the container. 
  
  The SSH server in the container looks for the following executables in absolute locations or the <code>PATH</code> environment variable:
  <ul>
  
negative.code: 
  #### Step 2: Deploy the GCP Image
  
  Run the following command to deploy your GCR image using the cf CLI:
  `CF_DOCKER_PASSWORD="$(cat key.json)" cf push APP-NAME --docker-image docker://MY-REGISTRY-URL/MY-PROJECT/MY-IMAGE-NAME --docker-username _json_key`
  <br>Replace the placeholder values in the command as follows:
  
  