Inclusive language

Author: VMWare-JasonAndrew

CONTRIBUTING.md

@@ -27,7 +27,7 @@ git push origin my-new-feature
 
 ### Updating pull requests
 
-If your PR fails to pass CI or needs changes based on code review, VMware recommends squashing these changes into existing commits.
+If your PR fails to pass CI or needs changes based on code review, squashing these changes into existing commits.
 
 If your pull request contains a single commit or your changes are related to the most recent commit, you can amend the commit.
 

bosh-release.html.md.erb

@@ -57,8 +57,7 @@ a managed service deployment using the [Tile Generator](tile-generator.html)'s
 support for `docker-bosh` packages. You can deploy pre-existing
 Docker images into BOSH-managed VMs on the <%= vars.platform_name %> infrastructure.
 
-While this is a great, easy way to deploy your service on <%= vars.platform_name %>, we do not
-recommend this as a long-term, production-ready solution. There is really no
+While this is a great, easy way to deploy your service on <%= vars.platform_name %>, this is not a long-term, production-ready solution. There is really no
 benefit of running your service in containers on the VMs, and it does have
 a number of operational ("day 2") drawbacks:
 
@@ -75,7 +74,7 @@ images you deploy.
 After the basic BOSH release is in place, additional features for logging
 help operators run the service. For logging information, see
 [syslog-release](https://github.com/cloudfoundry/syslog-release).
-<%= vars.company_name %> recommends you expose the property `syslog.migration.disabled` using the
+Expose the property `syslog.migration.disabled` using the
 tile's forms because not all customers configure syslog draining.
 
 Logs written under the expected BOSH location `/var/vcap/sys/log` are forwarded

brokered.html.md.erb

@@ -32,4 +32,4 @@ a good way to publish a first tile that adds real value for your customers who h
 
 * After you have the individual components for your brokered service integration, you can work through  [Building Your First Tile](./index.html#tile-steps) to create your tile.
 
-At any level of integration, <%= vars.company_name %> recommends and supports using [Concourse](./concourse.html) for continuous integration during development.
+At any level of integration, use [Concourse](./concourse.html) for continuous integration during development.

concourse.html.md.erb

@@ -9,7 +9,6 @@ There are two ways to do CI testing on your tile:
 
 + Use the Tile Dashboard provided as a service by the <%= vars.company_name %> ISV team.<br>
   See [Use Tile Dashboard CI to Test Your Tile](#dashboard) below.<br>
-  This is the method recommended by <%= vars.company_name %>.
 + Set up and use your own Concourse pipeline.<br>
   See [Set Up a concourse pipeline and test your tile](#concourse) below.<br>
   New partners work on only one tile at a time.

dev-workflow.html.md.erb

@@ -3,7 +3,7 @@ title: Development workflow for your tile
 owner: OpsMan
 ---
 
-This document references topics that follow <%= vars.company_name %>'s recommended tile development workflow in [Building Your First Tile](./index.html#tile-steps).
+This document references topics that follow <%= vars.company_name %>'s tile development workflow in [Building Your First Tile](./index.html#tile-steps).
 
 ## <a id="contents"></a> Development workflow
 

environments.html.md.erb

@@ -20,7 +20,7 @@ of BOSH that can manage virtual machines and BOSH releases for you.
 purpose.
 
 Between these two components, you will have everything you must develop
-tiles, except for Ops Manager. But if you followed the recommended workflow in [Building Your First Tile](index.html#tile-steps) you will not need an actual full
+tiles, except for Ops Manager. But if you followed the workflow in [Building Your First Tile](index.html#tile-steps) you will not need an actual full
 <%= vars.platform_name %> environment until the later phases of your development.
 
 ### <a id='setup-boshlite'></a> Setting up BOSH-Lite

managed.html.md.erb

@@ -23,8 +23,7 @@ To integrate your service at this level, you will have to learn about stemcells,
 
 ### <a id="managed-mvp"></a> Minimal viable product
 
-For a Minimal Viable Product (MVP) version of a managed service, we typically
-recommend that you aim for a single, shared service instance, and don't yet
+For a Minimal Viable Product (MVP) version of a managed service, you should aim for a single, shared service instance, and don't yet
 worry too much about High Availability of this instance. This integration level is mostly about getting the BOSH packaging, deployment, and monitoring working
 correctly.
 
@@ -48,4 +47,4 @@ your persistent storage across those as well.
 
 * The [Tile generator](./tile-generator.html) tool automatically creates the life cycle errands that can run after a <%= vars.platform_name %> tile is deployed or before it is removed. Operators control which errands run the next time they click **Apply Changes** to redeploy. See the [Errands](./tile-errands.html) topic for how <%= vars.platform_name %> operators control when errands run, and how to set default errand run rules in the tile.
 
-At any level of integration, <%= vars.company_name %> recommends and supports using [Concourse](./concourse.html) for continuous integration during development.
+At any level of integration, use [Concourse](./concourse.html) for continuous integration during development.

nozzle.html.md.erb

@@ -81,7 +81,7 @@ A service tile can install a nozzle as either a managed service, with package ty
 
 ### <a id="develop"></a> Develop a Nozzle
 
-<%= vars.company_name %> recommends developing a nozzle in Go to use the
+You must develop a nozzle in Go to use the
 [NOAA library](https://github.com/cloudfoundry/noaa).
 NOAA does the heavy lifting of establishing
 an authenticated websocket connection to the logging system and de-serializing the protocol buffers.

on-demand.html.md.erb

@@ -29,7 +29,7 @@ To create their tile, the tile author then feeds their service adapter and the B
 
 * Once you have the individual components for your brokered service integration, you can work through [Building Your First Tile](./index.html#tile-steps) to create your tile.
 
-At any level of integration, <%= vars.company_name %> recommends and supports using [Concourse](./concourse.html) for continuous integration during development.
+At any level of integration, you must use [Concourse](./concourse.html) for continuous integration during development.
 
 ### <a id="dynamic-ha"></a> High availability
 

pcf-command.html.md.erb

@@ -36,7 +36,7 @@ credentials of a "claimed" <%= vars.platform_name %> pool resource to the CI pip
 For interactive use, this means that you will have to create a `metadata`
 file in the directory where you run the `pcf` command.
 
-<p class='note'><%= vars.company_name %> recommends that you do <strong>not</strong> create this file inside your git or other version control system repository, as you do not want to accidentally commit these credentials to version control.</p>
+You should not create this file inside your git or other version control system repository, as you do not want to accidentally commit these credentials to version control.</p>
 
 ##<a id="commands"></a> Commands
 

property-template-references.html.md.erb

@@ -358,9 +358,7 @@ A description of the tile.
 
 The order in which a tile appears on the dashboard. The BOSH Director always appears at rank 100.
 
-For your tile to appear to the right of BOSH Director, you must set this value to an integer less than 100.
-
-<%= vars.recommended_by %> recommends that you set it to 1.
+For your tile to appear to the right of BOSH Director, you must set this value to an integer less than 100.  You should set it to 1.
 
 If all tiles have the same rank, Ops Manager sorts them alphabetically.
 
@@ -400,7 +398,7 @@ stemcell_criteria
   enable_patch_security_updates: false
 ```
 
-<%= vars.recommended_by %> recommends setting the `enable_patch_security_updates` property to `true`. If you set the property to `false`, your tile does not receive security patches through automatic stemcell updates.
+You should set the `enable_patch_security_updates` property to `true`. If you set the property to `false`, your tile does not receive security patches through automatic stemcell updates.
 
 You do not specify which IaaS the stemcell targets. This keeps your product template IaaS agnostic so that one product template can be deployed on any IaaS.
 

releases.html.md.erb

@@ -40,7 +40,7 @@ To enter Closed Beta, a product must meet the following requirements:
 
 * The product must fulfill its promised feature set, and perform as wanted.
 
-<%= vars.company_name %> also recommends that any Closed Beta product include an easy way for users to provide feedback to the product developer.
+Aa Closed Beta product should include an easy way for users to provide feedback to the product developer.
 
 ### Steps to Release
 To create a new Closed Beta release for your product:

runtime-config.html.md.erb

@@ -70,7 +70,7 @@ For more information about runtime config keys, see
 
 For more information about top-level properties in the tile manifest, see [Top-Level Properties](./property-template-references.html#top-level).
 
-<p class="note"><strong>Note:</strong> The names you choose must be unique across a deployment. <%= vars.company_name %> recommends appending your product name or another unique identifier to each of the named items in the <code>runtime_configs</code> section.</p>
+Append your product name or another unique identifier to each of the named items in the <code>runtime_configs</code> section.</p>
 
 
 ## <a id="delete"></a>Delete a runtime config

stages.html.md.erb

@@ -11,8 +11,7 @@ integration level increases. But none of the higher levels is required. You can
 stop service integration and declare it finished (enough) after any of these:
 
 When integrating third-party software with Cloud Foundry, the effort
-typically progresses through increasing levels of integration. <%= vars.company_name %> recommends
-this staged approach because it allows early feedback on the value and the
+typically progresses through increasing levels of integration. This staged approach because it allows early feedback on the value and the
 design of the integration, which helps make better decisions about future
 stages.
 

testing.html.md.erb

@@ -10,8 +10,8 @@ Here's recommended testing practices for <%= vars.platform_name %> tile develope
 Good testing assures tile developers that their product installs and runs properly on diverse platforms
 and assures platform operators that the tile they install can provide its service on their platform.
 
-<%= vars.company_name %> recommends a pyramid structure for testing, starting with unit tests and stepping up to successively broader and more automated levels of integration.
-<%= vars.company_name %> uses and recommends [Concourse](./concourse.html) for creating build pipelines that follow this test structure.
+Arrange fir a pyramid structure for testing, starting with unit tests and stepping up to successively broader and more automated levels of integration.
+Use [Concourse](./concourse.html) for creating build pipelines that follow this test structure.
 Other continuous integration tools must support a pyramid testing approach.
 
 ### <a id="pyramid"></a> Tile test pyramid

tile-reference/property-blueprints/_collection.html.erb

@@ -72,7 +72,7 @@ This holds multiple records of a group of custom defined properties.
         <li>Any text box ending in <code>name</code></li>
       </ul>
       <br>
-      <%= vars.recommended_by %> recommends including a logical key and setting
+     You must include a logical key and setting
       <code>freeze_on_deploy: true</code> in each collection where you want to
       target “update” and “delete and add” operations separately.
     </td>

tools.html.md.erb

@@ -2,7 +2,7 @@
 title: Tile development tools reference
 owner: Services
 ---
-Here's tile development tools that <%= vars.company_name %> uses and recommends for tile development.
+Here's tile development tools for tile development.
 
 * [Development environments](/docs-tiledev/environments.html) including simple standalone tools to a full <%= vars.platform_name %> development environment.