Bugzilla link fixes

Author: bobbygeeze

concourse.html.md.erb

@@ -89,10 +89,9 @@ There are two ways that you can configure the tile on the Tile Dashboard:
 
 To log in to the Tile Dashboard and go to the configuration page:
 
-1.  Log in to your PivotalPartners.slack.com account.
+1. Log on to your PivotalPartners.slack.com account.
 
-2. Go to the Tile Dashboard URL:
-   [tile-dashboard.cfapps.io/static/index.html#/environments](https://tile-dashboard.cfapps.io/static/index.html#/environments).
+2. Go to the Tile Dashboard URL.
 
     ![alt-text="The icons named pie-20, pie-21, and others on a list."](img/pie-environments.png)
 
@@ -189,7 +188,7 @@ To specify the UAA users:
 
 1. At the bottom of the configuration page, click **+** to expand the box and view the text boxes.
 
-    ![alt-text="The bottom of page shows plus button used to expand uaa properties form."](img/uaa-properties-collapsed.png)
+    ![alt-text="The bottom of the page shows plus button used to expand uaa properties form."](img/uaa-properties-collapsed.png)
 
 2.  Enter user name, password, and groups for the UAA user.
 
@@ -232,7 +231,7 @@ that the Tile Dashboard can reach, that is, it must be Internet-facing.
 ## <a id="concourse"></a> Set up a Concourse pipeline and test your tile
 
 The [Tile Dashboard CI](#tile-dashboard-ci) that <%= vars.company_name %> runs for its technical partnership program members
-uses the CI tool [Concourse](http://concourse.ci/) to verify that partner products continue
+uses the CI tool [Concourse](https://tanzu.vmware.com/developer/guides/concourse-gs/) to verify that partner products continue
 to work with every new release of the platform.
 
 You can also follow the pointers as shown later in this topic to set up your own Concourse CI pipeline
@@ -250,7 +249,7 @@ the [Tile Dashboard CI](#tile-dashboard-ci) servers can host your pipeline
 and provide S3 storage to exchange artifacts with your own servers.
 
 If you set up your own Concourse server,
-see the instructions in [Concourse: Setup & Operations](https://concourse-ci.org/setup-and-operations.html).
+see the instructions in [Concourse: Setup & Operations](https://concourse-ci.org/index.html).
 
 ### <a id="pipeline"></a> Create a Concourse pipeline for your tile
 

create-credhub-vars.html.md.erb

@@ -5,12 +5,11 @@ owner: CredHub
 
 You can use CredHub to manage variables in the context of a larger deployment, and create new variables.
 
-## <a id='background'></a> CredHub background
-
-When a tile author defines a top-level `variables` section in the product template, Ops Manager passes the `variables` section to the
+When a tile author defines a top-level `variables` section in the product template, Ops Manager passes
+the `variables` section to the
 product manifest.
 
-Tile authors can define variables in the product template as follows:
+You can define variables in the product template as follows:
 
 ```
 variables:
@@ -68,7 +67,7 @@ The manifest excerpt includes references to two credentials, <code>EXAMPLE-PASSW
 
 When this manifest is deployed, the BOSH Director retrieves the stored variables and replaces them with the
 credential values associated with each variable. The <code>EXAMPLE-TLS</code> variables include
-property accessors, so only the `certificate` and `private_key` components are interpolated.
+property accessors, because only the `certificate` and `private_key` components are interpolated.
 
 ```
 name: demo-deploy

credhub.html.md.erb

@@ -16,9 +16,10 @@ See the [CredHub documentation](https://docs.cloudfoundry.org/credhub/index.html
 
 Many <%= vars.platform_name %> components use credentials to authenticate connections, and <%= vars.platform_name %> installations often have hundreds of active credentials. Secure credential management is essential to prevent data and security breaches.
 
-In <%= vars.platform_name %> v1.11.0 and later, CredHub runs on the BOSH VM, alongside the BOSH Director and UAA. Ops Manager v1.11 stores its credentials in CredHub,
-and users can retrieve them using the CredHub API or the **Credentials** tab of the BOSH Director tile.
-Tile developers can embed CredHub calls in [manifest snippets](#snippets) and <%= vars.app_runtime_abbr %> apps can retrieve credentials using the CredHub API.
+In <%= vars.platform_name %> v1.11.0 and later, CredHub runs on the BOSH VM, alongside the
+BOSH Director and UAA. Ops Manager v1.11 and later stores its credentials in CredHub,
+and you can retrieve them using the CredHub API or the **Credentials** tab of the BOSH Director tile.
+You can embed CredHub calls in [manifest snippets](#snippets) and <%= vars.app_runtime_abbr %> apps can retrieve credentials using the CredHub API.ile developers
 
 For more information about variable names and values, see [Fetching variable names and values](./get-credhub-vars.html) for how to fetch variable names and values using the CredHub API.
 
@@ -52,7 +53,7 @@ use the JavaScript migration process. After a successful migration, Ops Manager
 
 For more information about migrating Credhub credentials, see [Migrating existing credentials to CredHub](./migrating-credhub-credentials.html).
 
-For more information about the Credhub API, see [CredHub API](https://credhub-api.cfapps.io), the [CredHub CLI GitHub repository](https://github.com/cloudfoundry-incubator/credhub-cli), and the [CredHub Release GitHub repository](https://github.com/pivotal-cf/credhub-release).
+For more information about the Credhub API, see the [CredHub CLI GitHub repository](https://github.com/cloudfoundry-incubator/credhub-cli), and the [CredHub Release GitHub repository](https://github.com/pivotal-cf/credhub-release).
 
 ## <a id="api-variables"></a>Fetching variable names and values
 
@@ -62,7 +63,7 @@ For more information about variable names and values, see <a href="./get-credhub
 
 ## <a id="snippets"></a> CredHub in manifest snippets
 
-Tile developers can embed CredHub in product template and job template manifest snippets using
+You can embed CredHub in product template and job template manifest snippets using
 [triple-parenthesis notation](./property-template-references.html#job-manifest):
 
 ```
@@ -82,7 +83,7 @@ Tile developers can embed CredHub in product template and job template manifest
 
 * Using CredHub to generate new credentials.
 
-Tile authors can choose to wait until <%= vars.platform_name %> supports some or all of these features before incorporating CredHub into their service.
+You can choose to wait until <%= vars.platform_name %> supports some or all of these features before incorporating CredHub into their service.
 
 ## <a id="resources"></a> CredHub resources
 

environments.html.md.erb

@@ -18,8 +18,7 @@ for Pivotal Technical Partnership Program (PTPP) program members to develop thei
 
 To use your assigned PIE environment:
 
-1. Log in to the <%= vars.company_name %> [Tile Dashboard](https://tile-dashboard.cfapps.io/)
-using the credentials that you use for [Partners Slack](https://pivotalpartners.slack.com/).
+1. Log on to the <%= vars.company_name %> Tile Dashboard using the credentials that you use for [Partners Slack](https://pivotalpartners.slack.com/).
 
 1. Click the `pie-xx` environment assigned to you.
 

ssi-creds-tiledev.html.md.erb

@@ -196,7 +196,8 @@ do the following:
 
 1. In your service broker code, locate where your broker handles binding requests from the CC.
 
-1. Add code that authenticates your service broker to CredHub using OAuth2 tokens from UAA. Each call to the CredHub API must include an authorization header. For more information about CredHub authentication, see the [CredHub API documentation](https://docs.cloudfoundry.org/api/credhub/version/2.9/).
+1. Add code that authenticates your service broker to CredHub using OAuth2 tokens from UAA. Each call to the CredHub API must include an authorization header. For more information about
+CredHub authentication, see the [Authentication](https://docs.cloudfoundry.org/api/credhub/version/2.9/#_authentication) section of the CredHub API documentation.
 
 <p class="note">
 <span class="note__title">Note</span>
@@ -226,17 +227,17 @@ See the following example for how to format your API call:
     -H 'Content-type: application/json'
     ```
 
-    Where:
+Where:
+  * `CREDHUB.INTERNAL_URL` and `CREDHUB.PORT` are the address and port of CredHub.
 
-    * `CREDHUB.INTERNAL_URL` and `CREDHUB.PORT` are the address and port of CredHub.
-    * `CLIENT-IDENTIFIER` is a value provided by the service broker to uniquely identify the broker.
-    * `SERVICE-IDENTIFIER` is the name of the service offering as shown in the services catalog.
-    * `BINDING-GUID` is the GUID created by the CC and passed to the service broker in the service binding request.
-    * `CREDENTIAL-NAME` is a value provided by the service broker to name the credential.
-    * `SERVICE-URL` is the URL of your service.
-    * `USERNAME` and `PASSWORD` are your binding credentials.
+  * `CLIENT-IDENTIFIER` is a value provided by the service broker to uniquely identify the broker.
+  * `SERVICE-IDENTIFIER` is the name of the service offering as shown in the services catalog.
+  * `BINDING-GUID` is the GUID created by the CC and passed to the service broker in the service binding request.
+  * `CREDENTIAL-NAME` is a value provided by the service broker to name the credential.
+  * `SERVICE-URL` is the URL of your service.
+  * `USERNAME` and `PASSWORD` are your binding credentials.
 
-    For further reference, see the [Set Credentials](https://docs.vmware.com/en/VMware-Tanzu-Application-Service/<%= vars.current_major_version %>/tas-for-vms/secure-si-creds.html) section of the CredHub API documentation.
+  For further reference, see the [Set Credentials](https://docs.vmware.com/en/VMware-Tanzu-Application-Service/4.0/tas-for-vms/secure-si-creds.html) section of the CredHub API documentation.
 
 1. Grant your application permission to read the credential from CredHub:
 
@@ -255,7 +256,7 @@ See the following example for how to format your API call:
 
     Where `APP-GUID` is the GUID of the Cloud Foundry application being used
 
-1. Edit your service broker so that it returns a reference to the stored credentials in response to the
+2. Edit your service broker so that it returns a reference to the stored credentials in response to the
 binding request from the CC. Return the credentials as a single key `credhub-ref` with thee value formatted
 as `/c/CLIENT-IDENTIFIER/SERVICE-IDENTIFIER/BINDING-GUID/CREDENTIAL-NAME`.
 

tile-upgrades.html.md.erb

@@ -19,7 +19,7 @@ constraints.
 
 Changing the value of<code>single_az_only</code> for jobs started by your tile can cause data loss
 for  upgrades to Ops Manager v1.7 versions later than v1.7.20, or v1.8 versions later than v1.8.12.
-To avoid this, contact <a href="https://tanzu.vmware.com/support">Support</a>.
+To avoid this, contact [VMware Support](https://tanzu.vmware.com/support.html).
 
 ## <a id='import'></a> Update Values or Property Names Using JavaScript