Note change

Author: VMWare-JasonAndrew

README.md

@@ -4,7 +4,8 @@ This repo is for Tile Developer Guide content.
 
 ## Which branch to use?
 
-**Note**: Provide instructions in your PRs to indicate which branches you want Docs to apply your commits to.
+>**Note**
+>If you are using the Provide instructions in your PRs to indicate which branches you want Docs to apply your commits to.
 
 | Branch name | Use for… |
 |-------------| ------|

environments.html.md.erb

@@ -27,7 +27,8 @@ tiles, except for Ops Manager. But if you followed the workflow in [Building You
 
 - [Install BOSH-Lite](https://github.com/cloudfoundry/bosh-lite)
 
-	<p class="note"><strong>Note:</strong> For this type of development environment, you only need BOSH-Lite itself to deploy managed service releases. You do not need to follow the instructions to Deploy Cloud Foundry in BOSH-Lite, as Cloud Foundry is provided by the <%= vars.product_dev_local %> installation above.</p>
+>**Note**
+>For this type of development environment, you only need BOSH-Lite itself to deploy managed service releases. You do not need to follow the instructions to Deploy Cloud Foundry in BOSH-Lite, as Cloud Foundry is provided by the <%= vars.product_dev_local %> installation above.
 
 ### <a id='setup-pcfdev'></a> Setting up <%= vars.product_dev_local %>
 

migrating-credhub-credentials.html.md.erb

@@ -38,7 +38,9 @@ The following table lists the Ops Manager credential types you can migrate to Cr
   </tr>
 </table>
 
-<p class="note"><strong>Note</strong>: CredHub does not retain the salt when migrating <code>salted_credentials</code>.</p>
+>**Note**
+>CredHub does not retain the salt when migrating <code>salted_credentials
+
 
 See [Property and template references](./property-template-references.html#secret) for more information about credential types.
 
@@ -94,8 +96,11 @@ following the naming conventions discussed in the [Update Values or Property Nam
             type: password
         ```
 
-        <p class="note"><strong>Note</strong>: While the property blueprint refers to the above type as <code>secret</code>, BOSH refers to the type as <code>password</code>. See the
-        <a href="#cred-types">CredHub Credential Types</a> table at the beginning of this topic for more information about credential types.</p>
+
+>**Note**
+>While the property blueprint refers to the above type as <code>secret</code>, BOSH refers to the type as <code>password</code>. See the <a href="#cred-types">CredHub Credential Types</a> table at the beginning of this topic for more information about credential types.
+
+
 
 1. In your manifest snippet, replace the existing secret value with the new triple-parenthesis syntax.
     * Remove the existing secret from the manifest snippet:
@@ -110,6 +115,6 @@ following the naming conventions discussed in the [Update Values or Property Nam
         secret: ((( SECRET-VARIABLE )))
         ```
 
-1. Run a [test deploy](./testing.html) of your tile.
+2. Run a [test deploy](./testing.html) of your tile.
 
-1. Use an API endpoint to confirm that the credential is stored in the variable. For more information about the endpoint, see [Fetching Variable Names and Values](./get-credhub-vars.html).
+3. Use an API endpoint to confirm that the credential is stored in the variable. For more information about the endpoint, see [Fetching Variable Names and Values](./get-credhub-vars.html).

migrating-syslog-configuration.html.md.erb

@@ -148,5 +148,6 @@ configuration, do one of the following:
     For more information about the `syslog_configuration` API endpoint, see
     [Retrieving syslog configuration for a product](https://docs.pivotal.io/platform/2-10/opsman-api/#tag/Syslog-Configuration/paths/~1api~1v0~1staged~1products~1{product_guid}~1syslog_configuration/get).
 
-<p class="note"><strong>Note:</strong> In the next version of your product, remove
-  the deprecated syslog configuration properties.</p>
+>**Note**
+>In the next version of your product, remove
+  the deprecated syslog configuration properties.<

odb-resource-defaults.html.md.erb

@@ -3,7 +3,9 @@ title: Configuring disk and VM type defaults for on-demand service tiles
 owner: Ops Manager
 ---
 
-<p class="note"><strong>Note</strong>: Ops Manager 2.0 and later supports defining VM and disk type defaults and constraints.</p>
+>**Note**
+>Ops Manager 2.0 and later supports defining VM and disk type defaults and constraints.
+
 
 Here you will find how tile authors can configure the dropdown menu items for VM types and persistent disk types in their tile.
 

property-template-references.html.md.erb

@@ -440,10 +440,12 @@ The following keys are supported:
 - `name`: The name of the tile required by your tile. This is a required key.
 - `version`: The version range required by your tile. This is a required key.
 - `optional`: This is an optional key that defaults to false.
-  <p class="note warning"><strong>Warning:</strong> The <code>optional</code> key was introduced in Ops Manager v2.8.
-  It is ignored in earlier versions.
-  This means that declared dependencies are required in Ops Manager v2.7 and earlier.
-  </p>
+
+>**Caution**
+>It is ignored in earlier versions.
+This means that declared dependencies are required in Ops Manager v2.7 and earlier.
+
+
 
 For example:
 
@@ -981,7 +983,8 @@ Jobs require many different settings to function properly. That is the core of w
 
 Ops Manager does not require tile authors to provide `vm_credentials` in the `property_blueprints` for each `job_type`. This is because `vm_credentials` are generated automatically. You can find them in the release manifest.
 
-<p class="note"><strong>Note:</strong> Ops Manager ignores <code>static_ip</code> and <code>dynamic_ip</code> keys. To configure the static IPs of a <code>job_type</code>, create a property blueprint with <code>name: static_ips</code> and <code>type: ip_ranges</code>.<br><code>static_ips</code> is a special keyword that Ops Manager uses to find static IPs and pass them to the BOSH manifest. For more information about <code>ip_ranges</code>, see <a href="#ip-ranges">ip_ranges</a>.</p>
+>**Note**
+>Ops Manager ignores <code>static_ip</code> and <code>dynamic_ip</code> keys. To configure the static IPs of a <code>job_type</code>, create a property blueprint with <code>name: static_ips</code> and <code>type: ip_ranges</code>.<br><code>static_ips</code> is a special keyword that Ops Manager uses to find static IPs and pass them to the BOSH manifest. For more information about <code>ip_ranges</code>, see <a href="#ip-ranges">ip_ranges</a>.
 
 ```
 job_types:
@@ -1259,7 +1262,9 @@ You can give users control of balancing jobs across availability zones (AZs) by
 
 To limit a job to a single AZ, set `single_az_only` to `true`.
 
-<p class="note warning"><strong>Warning:</strong> If you change the <code>single_az_only</code> setting, your VMs may switch AZs. This change can cause an orphaned disk.</p>
+>**Caution** If you change the <code>single_az_only</code> setting, your VMs may switch AZs. This change can cause an orphaned disk.
+
+
 
 ### <a id='job-max-in-flight'></a> max_in_flight
 
@@ -1295,7 +1300,8 @@ The resources you can set are:
 
 For examples of supported constraint types, see [integer](#integer).
 
-<p class="note"><strong>Note:</strong> If you set the <code>default</code> property for <code>persistent_disk</code> to <code>0</code>, users cannot edit this value and the <strong>Resource Config</strong> pane in the Ops Manager tile displays <strong>None</strong> under the persistent disk text box.</p>
+>**Note**
+>If you set the <code>default</code> property for <code>persistent_disk</code> to <code>0</code>, users cannot edit this value and the <strong>Resource Config</strong> pane in the Ops Manager tile displays <strong>None</strong> under the persistent disk text box.
 
 ### <a id='job-instance-def'></a> instance_definition
 
@@ -1312,7 +1318,9 @@ For example, your tile uses Amazon Relational Database Service (RDS) instead of
 
 For examples of supported constraint types, see [integer](#integer).
 
-<p class="note"><strong>Note:</strong> If you are using the <code>zero_if</code> property, you should not set the <code>may_only_increase</code> constraint to <code>true</code>.</p>
+>**Note**
+>If you are using the <code>zero_if</code> property, you should not set the <code>may_only_increase</code> constraint to <code>true</code>.
+
 
 ### <a id='job-manifest'></a> Manifest
 
@@ -1417,7 +1425,8 @@ Use the `current_record` property within a collection record to refer to other p
 
 For example, the properties in the `for_routing` named manifest refer to the values for `name`, `private_key`, `public_key`, and `certificate` within this record only.
 
-<p class="note"><strong>Note:</strong> The <code>current_record</code> property is reserved. You cannot create a new property named <code>current_record</code>.</p>
+>**Note**
+>If you are using the The <code>current_record</code> property is reserved. You cannot create a new property named <code>current_record</code>.
 
 After defining a named manifest, you can reference it using a manifest snippet in the following format:
 

ssi-creds-tiledev.html.md.erb

@@ -38,7 +38,8 @@ The sections below describe an example implementation of how to add SSI credenti
 
 To use runtime CredHub, your service tile needs to retrieve the location of the CredHub server, which is published in the <%= vars.app_runtime_abbr %> tile, through a BOSH link.
 
-<p class="note"><strong>Note</strong>: BOSH Links let multiple jobs share deployment-time configuration properties. This helps to avoid redundant configurations in BOSH releases and deployment manifests. For more information about BOSH Links, see <a href="http://docs.pivotal.io/tiledev/1-11/release-notes.html#bosh-links">BOSH Links</a>.</p>
+>**Note**
+>If you are using the BOSH Links let multiple jobs share deployment-time configuration properties. This helps to avoid redundant configurations in BOSH releases and deployment manifests. For more information about BOSH Links, see <a href="http://docs.pivotal.io/tiledev/1-11/release-notes.html#bosh-links">BOSH Links</a>.
 
 ### <a id="spec"></a> Update spec file and templates
 
@@ -214,4 +215,5 @@ To activate your service broker to store binding credentials in runtime CredHub
     }
     ```
 
-<p class="note"><strong>Note:</strong> Java Virtual Machine (JVM) apps can use <a href="https://projects.spring.io/spring-credhub">Spring CredHub</a> to access the CredHub API.</p>
+>**Note**
+>If you are using the Java Virtual Machine (JVM) apps can use <a href="https://projects.spring.io/spring-credhub">Spring CredHub</a> to access the CredHub API.

testing.html.md.erb

@@ -38,7 +38,8 @@ For <%= vars.platform_name %> tiles, a typical test pyramid progresses as follow
   - Confirm manually that the tile wires property blueprints to the expected pane and form controls in the UI.
   - Test your environment using one of the environments described in [Development Environments](./environments.html)
 
-<p class="note"><strong>Note</strong>: System tests might incur costs from using third party services, IaaS resources, and others.</p>
+>**Note**
+>System tests might incur costs from using third party services, IaaS resources, and others.
 
 ### <a id="smoke"></a> Smoke tests
 

tile-errands.html.md.erb

@@ -22,7 +22,9 @@ To save deployment time, operators can set [errand run rules](#run-rules) that d
 
 ## <a id="colocated"></a>Define a co-located errand
 
-<p class="note"><strong>Note</strong>: Ops Manager v2.0 and later supports co-located errands.</p>
+>**Note**
+>System tests might incur costs from using third party services, IaaS resources, and others.
+
 
 Instead of deploying a new VM for each errand, co-located errands run on an existing VM.
 Errands can run alongside other jobs on a VM, and multiple errands can be co-located on the same VM.

tile-generator.html.md.erb

@@ -97,7 +97,8 @@ For a 7-minute introduction into what Tile Generator is and does, see
         This puts the `tile` and `pcf` commands in your `PATH` when the virtualenv is active.
         To deactivate the virtualenv, run the command `deactivate`.
 
-        <p class="note"><strong>Note</strong>: To upgrade Tile Generator, run <code>pip install tile-generator --upgrade</code>
+        >**Note**
+        >To upgrade Tile Generator, run <code>pip install tile-generator --upgrade</code>
           with the virtualenv activated.</p>
 
 
@@ -106,7 +107,8 @@ For a 7-minute introduction into what Tile Generator is and does, see
 3. From within the root directory of the project for which you want to create a tile,
 initialize the directory as a tile repository by running the following commands:
 
-    <p class="note"><strong>Note</strong>: <%= vars.company_name %> recommends that you use a git repository.</p>
+    >**Note**
+    >If you are using the  <%= vars.company_name %> recommends that you use a git repository.</p>
 
     ```
     cd YOUR-PROD-DIRECTORY
@@ -164,7 +166,8 @@ You can build this sample using the following steps:
     tile build
     ```
 
-<p class="note"><strong>Note</strong>: The sample tile includes a Python app that is re-used in several packages,
+    >**Note**
+    >The sample tile includes a Python app that is re-used in several packages,
     sometimes as an app, sometimes as a service broker. One of the deployments (app3)
     uses the sample app inside a Docker image that is modified
     by the CI pipeline. If you edit the sample app, you have to build your own
@@ -304,8 +307,8 @@ of `app` or `docker-app`:
   enable_global_access_to_plans: true  # optional
 ```
 
-  <p class="note">
-    <strong>Note</strong>: Unless you specify the <code>enable_global_access_to_plans: true</code> option, your
+  >**Note**
+  >Unless you specify the <code>enable_global_access_to_plans: true</code> option, your
     broker's services do not appear in the user's Marketplaces.
     Operators have to use the <code>cf enable-service-access</code> command to allow
     specific users, orgs, and spaces to access your services.
@@ -656,10 +659,8 @@ package.
 Service instances provisioned this way survive updates, but are deleted
 when the tile is uninstalled.
 
-<p class="note"><strong>Note</strong>:  The name is the name of the provided <em>service, not the broker</em>.
-    In many cases these are not the same, and a single broker might even offer
-    multiple services. Use <code>cf service-access</code> to see the services and plans
-    offered by installed service brokers.</p>
+  >**Note**
+  >The name is the name of the provided <em>service, not the broker</em>. In many cases these are not the same, and a single broker might even offer multiple services. Use <code>cf service-access</code> to see the services and plans offered by installed service brokers.</p>
 
 If you do not specify a plan, Tile Generator uses the first plan
 listed for the service in the broker catalog. It is a good idea to always

tile-reference/property-blueprints/_rsa-cert-credentials.html.erb

@@ -25,14 +25,14 @@ This holds SSL certificate generated from root CA.
       list of domain names to use when auto-generating the RSA certificate.
       The first domain listed will be the value of the Common Name text box of the cert.
       The full list of domains will be the value of the Alternative Names text box of the cert.
-      See below for an example.
-      <p class="note">
-        <strong>Note:</strong> This property does not work with a selector property when <code>configurable: false</code> is set. For more information, see <a href="https://docs.pivotal.io/tiledev/2-10/release-notes.html#non-configurable-certs">Non-Configurable Certificates Are Invalid Within a Selector</a> in the release notes.
-      </p>
-    </td>
+      See the following for an example.
   </tr>
 </table>
 
+> Notes
+> This property does not work with a selector property when <code>configurable: false</code> is set. For more information, see <a href="https://docs.pivotal.io/tiledev/2-10/release-notes.html#non-configurable-certs">Non-Configurable Certificates Are Invalid Within a Selector</a> in the release notes.
+    </td>
+
 #### Accessors
 
 <table class="nice">

tile-structure.html.md.erb

@@ -67,7 +67,8 @@ Each form, or configuration pane, has `label` for the menu text, a `description`
 
 For each property, you can combine specifications for `name`, `type`, `default`, `configurable`, `options`, and `constraints`. For more information, see the [Form Properties](./property-template-references.html#form-properties) and [Property Blueprints](./property-template-references.html#property-blueprints) sections of the _Property and Template References_ topic.
 
-<p class="note"><strong>Note:</strong> In the tile installer <code>.yml</code> that Tile Generator creates, form properties appear in two locations: a <code>form_types</code> section that defines the contents and layout of the configuration interface, and a <code>property_blueprints</code> section that defines the corresponding text box value types and constraints.</p>
+>**Note**
+>In the tile installer <code>.yml</code> that Tile Generator creates, form properties appear in two locations: a <code>form_types</code> section that defines the contents and layout of the configuration interface, and a <code>property_blueprints</code> section that defines the corresponding text box value types and constraints.
 
 #### <a id='appearance'></a> Tile appearance
 
@@ -97,7 +98,10 @@ You can include both required and optional product dependencies for tiles.
 
 * **Required Dependencies**: Required dependencies are always required. To deploy the dependent tile, you must also deploy the dependency.
 
-* **Optional Dependencies**: Optional dependencies are only required if you upload both the dependent tile and the optional dependency to your environment. For example, a tile may be dependent on either <%= vars.app_runtime_abbr %> or <%= vars.k8s_runtime_full %> (<%= vars.k8s_runtime_abbr %>). If you define <%= vars.app_runtime_abbr %> and <%= vars.k8s_runtime_abbr %> as optional dependecies, you can upload either <%= vars.app_runtime_abbr %> or <%= vars.k8s_runtime_abbr %> to successfully deploy the dependent tile.<p class="note"><strong>Note:</strong> After the dependency is installed, it is mandatory even if marked as optional.</p>
+* **Optional Dependencies**: Optional dependencies are only required if you upload both the dependent tile and the optional dependency to your environment. For example, a tile may be dependent on either <%= vars.app_runtime_abbr %> or <%= vars.k8s_runtime_full %> (<%= vars.k8s_runtime_abbr %>). If you define <%= vars.app_runtime_abbr %> and <%= vars.k8s_runtime_abbr %> as optional dependecies, you can upload either <%= vars.app_runtime_abbr %> or <%= vars.k8s_runtime_abbr %> to successfully deploy the dependent tile.
+
+>**Note**
+>After the dependency is installed, it is mandatory even if marked as optionaass=l.
 
 Include product dependencies under `requires_product_versions` at the top of the `tile.yml` file. To add an optional dependency, use an `optional` text box under `requires_product_versions`. For example: