Fix contractions and other linting issues

Signed-off-by: Ian Maddaus <[email protected]>

Author: IanMadd

content/attribute_arrays.md

@@ -29,7 +29,7 @@ override_attributes(
 )
 ```
 
-But what if all of the web servers are not the same? What if some of the web servers required a single attribute to have a different value? You could store these settings in two locations, once just like the preceding example and once just like the following:
+But what if all of the web servers aren't the same? What if some of the web servers required a single attribute to have a different value? You could store these settings in two locations, once just like the preceding example and once just like the following:
 
 ```ruby
 override_attributes(
@@ -44,7 +44,7 @@ override_attributes(
 )
 ```
 
-But that is not efficient, especially because most of them are identical. The deep merge capabilities of Chef Infra Client allows attributes to be layered across cookbooks, recipes, roles, and environments. This allows an attribute to be reused across nodes, making use of default attributes set at the cookbook level, but also providing a way for certain attributes (with a higher attribute precedence) to be applied only when they are supposed to be.
+But that'sn't efficient, especially because most of them are identical. The deep merge capabilities of Chef Infra Client allows attributes to be layered across cookbooks, recipes, roles, and environments. This allows an attribute to be reused across nodes, making use of default attributes set at the cookbook level, but also providing a way for certain attributes (with a higher attribute precedence) to be applied only when they're supposed to be.
 
 For example, a role named `baseline.rb`:
 
@@ -115,7 +115,7 @@ to produce results like this:
          }
 ```
 
-Even though the `web.rb` file does not contain attributes and values for `minspareservers`, `maxspareservers`, `serverlimit`, `maxclients`, and `maxrequestsperchild`, the deep merge capabilities pulled them in.
+Even though the `web.rb` file doesn't contain attributes and values for `minspareservers`, `maxspareservers`, `serverlimit`, `maxclients`, and `maxrequestsperchild`, the deep merge capabilities pulled them in.
 
 ## Attribute Array Logic
 
@@ -153,7 +153,7 @@ role_or_environment 2 { :x => '1' , :y => '2' }
 { :x => '1', :y => '2' }
 ```
 
-When items cannot be merged through substitution, the original data is overwritten.
+When items can't be merged through substitution, the original data is overwritten.
 
 ### Addition
 

content/attribute_precedence.md

@@ -29,7 +29,7 @@ The attribute precedence order for the sources "roles" and "environments" are op
 Applying the role `override` first lets you use the same role in a set of environments.
 Applying the environment `override` on top of the role `override` lets you define a subset of these with environment-specific settings.
 
-This is useful if you have an environment that is different within a sub-set of a role. For example, the role for an application server may exist in all environments, but one environment may use a different database server.
+This is useful if you have an environment that's different within a sub-set of a role. For example, the role for an application server may exist in all environments, but one environment may use a different database server.
 
 {{< /note >}}
 
@@ -211,7 +211,7 @@ node.default['foo'] = {
 And some role attributes:
 
 ```ruby
-# Please do not ever do this in real code :)
+# Please don't ever do this in real code :)
 node.role_default['foo']['bar']['thing'] = 'otherstuff'
 ```
 
@@ -252,7 +252,7 @@ node.default['foo'] = {
 And some role attributes:
 
 ```ruby
-# Please do not ever do this in real code :)
+# Please don't ever do this in real code :)
 node.role_default['foo']['bar']['thing'] = 'otherstuff'
 ```
 
@@ -425,7 +425,7 @@ Given the following code structure:
 
 ```ruby
 node.default['foo']['bar'] = {'a' => 'b'}
-# Please do not ever do this in real code :)
+# Please don't ever do this in real code :)
 node.role_default['foo']['bar'] = {'c' => 'd'}
 node.default!['foo']['bar'] = {'d' => 'e'}
 ```
@@ -443,7 +443,7 @@ Given the following code structure:
 
 ```ruby
 node.default['foo']['bar'] = {'a' => 'b'}
-# Please do not ever do this in real code :)
+# Please don't ever do this in real code :)
 node.role_default['foo']['bar'] = {'c' => 'd'}
 node.force_default!['foo']['bar'] = {'d' => 'e'}
 ```
@@ -473,7 +473,7 @@ node.default['foo'] = {
 And some attributes:
 
 ```ruby
-# Please do not ever do this in real code :)
+# Please don't ever do this in real code :)
 node.role_default['foo']['bar']['baz'] = 55
 node.force_default['foo']['bar']['baz'] = 66
 ```

content/attribute_sources.md

@@ -10,7 +10,7 @@ draft = false
 +++
 <!-- markdownlint-disable-file MD036 -->
 
-Chef Infra Client evaluates attributes in the order that they are defined in the
+Chef Infra Client evaluates attributes in the order that they're defined in the
 run-list, including any attributes that are in the run-list as
 cookbook dependencies.
 
@@ -87,7 +87,7 @@ of the attribute priority methods:
 - `normal_unless`
 
 Use the `_unless` variants carefully (and only when necessary) because
-when they are used, attributes applied to nodes may become out of sync
+when they're used, attributes applied to nodes may become out of sync
 with the values in the cookbooks as these cookbooks are updated. This
 approach can create situations where two otherwise identical nodes end
 up having slightly different configurations and can also be a challenge
@@ -104,7 +104,7 @@ Use the following methods within the attributes file for a cookbook or within a
 
 ### attribute?
 
-A useful method that is related to attributes is the `attribute?`
+A useful method that's related to attributes is the `attribute?`
 method. This method will check for the existence of an attribute, so
 that processing can be done in an attributes file or recipe, but only if
 a specific attribute exists.

content/aws_marketplace.md

@@ -101,7 +101,7 @@ AWS provides five VPCs for each region. If you require more VPCs, please contact
    1. Set the stack creation options:
 
       Timeout
-      : If specified and stack creation is not completed in that time, CloudFormation will roll back the stack.
+      : If specified and stack creation isn't completed in that time, CloudFormation will roll back the stack.
 
       Termination Protection
       : Termination protection prevents a user from deleting a stack.
@@ -118,7 +118,7 @@ For additional information about these options, see [Amazon's documentation on C
 1. Open your browser and paste the Chef Automate URL, which will open an alert page.
 
 1. Select **Advanced** and continue.
-![Select 'advanced' to bypass the warning that the page is not secure](/images/NotSecurePage.png "Not Secure Page").
+![Select 'advanced' to bypass the warning that the page isn't secure](/images/NotSecurePage.png "Not Secure Page").
 
 1. Enter your **Username** and **Password** and select **Sign In**.
 ![ ](/images/chef_automate_login.png "Chef Automate Login")

content/azure_chef_cli.md

@@ -29,7 +29,7 @@ machines in Microsoft Azure.
 ### get-chef
 
 Use the `get-chef` command to get the details for the Azure Chef
-Extension that is running on the named virtual machine.
+Extension that's running on the named virtual machine.
 
 #### Syntax
 
@@ -78,7 +78,7 @@ This command has the following options:
 
 `-j JSON`, `--bootstrap-options JSON`
 
-: A JSON string that is added to the first run of a Chef Infra Client.
+: A JSON string that's added to the first run of a Chef Infra Client.
   For example:
 
   ```bash
@@ -208,7 +208,7 @@ The extension has the following options that can be provided in the
 
 `secret`
 
-: The encryption key that is used for values contained within a data bag item.
+: The encryption key that's used for values contained within a data bag item.
 
 `validation_client_name`
 

content/azure_powershell.md

@@ -22,7 +22,7 @@ on virtual machines in Microsoft Azure.
 ### Get-AzureVMChefExtension
 
 Use the `Get-AzureVMChefExtension` cmdlet to get the details for the
-Azure Chef Extension that is running on the named virtual machine.
+Azure Chef Extension that's running on the named virtual machine.
 
 #### Syntax
 
@@ -70,11 +70,11 @@ This cmdlet has the following options:
 
 `-AutoUpdateChefClient`
 
-: Automatically update . Set to `true` to automatically update the version of the Azure Chef Extension when the virtual machine is restarted. For example, if this option is enabled, a virtual machine that has version `1205.12.2.0` will be updated automatically to `1205.12.2.1` when it is published.
+: Automatically update . Set to `true` to automatically update the version of the Azure Chef Extension when the virtual machine is restarted. For example, if this option is enabled, a virtual machine that has version `1205.12.2.0` will be updated automatically to `1205.12.2.1` when it's published.
 
 `-BootstrapOptions <string>`
 
-: A JSON string that is added to the first run of a Chef Infra Client.
+: A JSON string that's added to the first run of a Chef Infra Client.
 
   For example:
 

content/azure_testdrive.md

@@ -22,7 +22,7 @@ product = ["client", "workstation", "automate"]
 
 ## Test Drive
 
-A **Test Drive** is a ready-to-go environment that allows you to experience Chef Automate for free, without an Azure subscription (You will need a [Microsoft account](https://signup.live.com/). The Test Drive comes already provisioned---you do not need to download, set up, or configure it---instead, you can spend two hours evaluating the user experience, key features, and benefits of the product.
+A **Test Drive** is a ready-to-go environment that allows you to experience Chef Automate for free, without an Azure subscription (You will need a [Microsoft account](https://signup.live.com/). The Test Drive comes already provisioned---you don't need to download, set up, or configure it---instead, you can spend two hours evaluating the user experience, key features, and benefits of the product.
 
 ### Get Started
 

content/chef_client_security.md

@@ -31,7 +31,7 @@ aliases = ["/chef_client_security.html", "/auth.html"]
 
 {{< warning >}}
 
-The following information applies to on-premises Chef Infra Server and does not apply to Hosted Chef.
+The following information applies to on-premises Chef Infra Server and doesn't apply to Hosted Chef.
 
 {{< /warning >}}
 
@@ -41,7 +41,7 @@ The following information applies to on-premises Chef Infra Server and does not
 
 Your organization may use a private Certificate Authority (CA) to generate SSL Certificates or they may create self-signed SSL certificates to use on internal networks or during software development and testing.
 
-The `trusted_certs` directory on Chef Workstation and in Chef Infra Client works as a trusted certificate store for all communication in the Chef Infra system. Chef Infra trusts all SSL certificates stored in this directory--including certificates that are not issued by a trusted Certificate Authority (CA).
+The `trusted_certs` directory on Chef Workstation and in Chef Infra Client works as a trusted certificate store for all communication in the Chef Infra system. Chef Infra trusts all SSL certificates stored in this directory--including certificates that aren't issued by a trusted Certificate Authority (CA).
 
 Place private and self-signed certificates in the `trusted_certs` directory to use them within Chef Infra Client and Workstation tools.
 
@@ -67,7 +67,7 @@ When you bootstrap a node, the Chef Infra Client copies the SSL certificates for
 
 Use the `SSL_CERT_FILE` environment variable to specify the location for the SSL certificate authority (CA) bundle for Chef Infra Client.
 
-A value for `SSL_CERT_FILE` is not set by default. Unless updated, the locations in which Chef Infra will look for SSL certificates are:
+A value for `SSL_CERT_FILE` isn't set by default. Unless updated, the locations in which Chef Infra will look for SSL certificates are:
 
 - Chef Infra Client: `/opt/chef/embedded/ssl/certs/cacert.pem`
 - Chef Workstation: `/opt/chef-workstation/embedded/ssl/certs/cacert.pem`

content/chef_compliance_phase.md

@@ -18,7 +18,7 @@ Chef Infra Client's Compliance Phase lets you automatically execute compliance a
 Existing audit cookbook users can migrate to the new Compliance Phase by removing the audit cookbook from their run_list and setting the `node['audit']['compliance_phase']` attribute to `true`.
 
 The Compliance Phase replaces the `audit cookbook` by integrating Chef InSpec compliance checks into the [Chef Infra Client run]({{< relref "chef_client_overview.md" >}})
-The Compliance Phase is designed to run on any node in your system that is set up--or [bootstrapped]({{< relref "install_bootstrap" >}})--for a `chef-client` run.
+The Compliance Phase is designed to run on any node in your system that's set up--or [bootstrapped]({{< relref "install_bootstrap" >}})--for a `chef-client` run.
 
 **New in Chef Infra Client 17.8**
 
@@ -176,7 +176,7 @@ The following examples:
 
 ### Reporters
 
-Reporters control what is done with the resulting report after the Chef InSpec run. Either a single value or a list of multiple values is supported. The default is the `cli` and `json-file` reporters.
+Reporters control what's done with the resulting report after the Chef InSpec run. Either a single value or a list of multiple values is supported. The default is the `cli` and `json-file` reporters.
 
 Reporters can send Compliance Phase results to:
 
@@ -303,7 +303,7 @@ There are two primary ways to pass Chef Infra node data to Chef InSpec run durin
 
 ##### Explicitly pass necessary data (recommended)
 
-Any data added to the `node['audit']['attributes']` hash will be passed as individual Chef InSpec attributes. This provides a clean interface between the Chef Infra client run and Chef InSpec profile, allowing for easy assignment of default values in the Chef InSpec profile. This method is especially recommended if the Chef InSpec profile is expected to be used outside of the context of Compliance Phase so it is made explicit to profile consumers what attributes are necessary. Set the attributes in your cookbook attributes file and then use them in your Chef InSpec profile.
+Any data added to the `node['audit']['attributes']` hash will be passed as individual Chef InSpec attributes. This provides a clean interface between the Chef Infra client run and Chef InSpec profile, allowing for easy assignment of default values in the Chef InSpec profile. This method is especially recommended if the Chef InSpec profile is expected to be used outside of the context of Compliance Phase so it's made explicit to profile consumers what attributes are necessary. Set the attributes in your cookbook attributes file and then use them in your Chef InSpec profile.
 
 Set the attributes in a cookbook attributes file:
 
@@ -322,7 +322,7 @@ environment = attribute('environment', description: 'The Chef Infra environment
 
 control 'debug-disabled-in-production' do
   title 'Debug logs disabled in production'
-  desc 'Debug logs contain potentially sensitive information and should not be on in production.'
+  desc 'Debug logs contain potentially sensitive information and shouldn't be on in production.'
   impact 1.0
 
   describe file('/path/to/my/app/config') do
@@ -337,7 +337,7 @@ end
 
 Compliance Phase can be configured to pass the Chef Infra node object as a Chef InSpec attribute named `chef_node`.
 
-While using the `chef_node` object provides the ability to write more flexible profiles, it is  difficult to reuse these profiles outside of the Compliance Phase. To reuse these profiles, you will need to understand how to pass in a single attribute containing Chef Infra-like data. Pass external data explicitly whenever possible.
+While using the `chef_node` object provides the ability to write more flexible profiles, it's  difficult to reuse these profiles outside of the Compliance Phase. To reuse these profiles, you will need to understand how to pass in a single attribute containing Chef Infra-like data. Pass external data explicitly whenever possible.
 
 To use this option, first set it in a wrapper cookbook:
 
@@ -482,7 +482,7 @@ default['audit']['quiet'] = false
 
 ### reporter
 
-Controls what is done with the resulting report after the Chef InSpec run. Accepts a single string value or an array of multiple values. The 'cli' reporter mimics the Chef InSpec command line output in your terminal, which lets you see your system's compliance status at the end of the Compliance Phase. Accepted values: 'chef-server-automate', 'chef-automate', 'json-file', 'audit-enforcer', 'cli'
+Controls what's done with the resulting report after the Chef InSpec run. Accepts a single string value or an array of multiple values. The 'cli' reporter mimics the Chef InSpec command line output in your terminal, which lets you see your system's compliance status at the end of the Compliance Phase. Accepted values: 'chef-server-automate', 'chef-automate', 'json-file', 'audit-enforcer', 'cli'
 
 ```ruby
 # set the reporter to Chef Automate
@@ -500,7 +500,7 @@ default['audit']['run_time_limit'] = 5.0
 
 ### result_include_backtrace
 
-When a Chef InSpec resource throws an exception, results contain a short error message and a detailed ruby stacktrace of the error. Default: false (does not send backtrace). Example:
+When a Chef InSpec resource throws an exception, results contain a short error message and a detailed ruby stacktrace of the error. Default: false (doesn't send backtrace). Example:
 
 ```ruby
 # include backtrace
@@ -509,7 +509,7 @@ default['audit']['result_include_backtrace'] = true
 
 ### result_message_limit
 
-Truncates any control result messages exceeding this character limit. Chef Automate has a 4 MB report size limit and cannot ingest reports exceeding this limitation. Chef InSpec will append this text at the end of any truncated messages: `[Truncated to 10000 characters]` Default: 10000.
+Truncates any control result messages exceeding this character limit. Chef Automate has a 4 MB report size limit and can't ingest reports exceeding this limitation. Chef InSpec will append this text at the end of any truncated messages: `[Truncated to 10000 characters]` Default: 10000.
 
 ```ruby
 default['audit']['result_message_limit] = 10000
@@ -557,7 +557,7 @@ Depending on your setup, there are some limits you need to be aware of. A common
 
 #### 401, 403 Unauthorized - bad clock
 
-Occasionally, the system date/time will drift between client and server. If this drift is greater than a couple of minutes, the Chef Infra Server will throw a 401 unauthorized and the request will not be forwarded to the Chef Automate server.
+Occasionally, the system date/time will drift between client and server. If this drift is greater than a couple of minutes, the Chef Infra Server will throw a 401 unauthorized and the request won't be forwarded to the Chef Automate server.
 
 On the Chef Infra Server you can see this in the following logs:
 
@@ -652,7 +652,7 @@ The 413 "Request Entity Too Large" error appears in both the stacktrace and the
 
 ## Troubleshooting
 
-Chef Automate sets the `logstash` limit to 10% of the system memory automatically as part of the `automate-ctl reconfigure` command execution. You have reached the java heap size(`-Xmx`) limit of `logstash` if a Chef InSpec report does not become available in Chef Automate and this error is in the `logstash` logs:
+Chef Automate sets the `logstash` limit to 10% of the system memory automatically as part of the `automate-ctl reconfigure` command execution. You have reached the java heap size(`-Xmx`) limit of `logstash` if a Chef InSpec report doesn't become available in Chef Automate and this error is in the `logstash` logs:
 
 ```text
 /var/log/delivery/logstash/current