Minor fixes in Workstation docs (#13) (#14)

(cherry picked from commit 41451f8)

Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
Co-authored-by: Ian Maddaus <IanMadd@users.noreply.github.com>

Author: github-actions[bot]

content/_index.md

@@ -31,7 +31,7 @@ Chef Workstation includes the following fully integrated tools:
 
 - **Chef CLI (`chef-cli`)**: Primary command-line interface for Chef development workflows, providing unified access to common Chef operations
 - **Chef Infra Client**: Latest release candidate of the Chef Infra Client, enabling infrastructure automation and configuration management
-- **Knife**: Essential tool for interacting with Chef Infra Server, managing nodes, cookbooks, roles, and other Chef objects
+- **knife**: Essential tool for interacting with Chef Infra Server, managing nodes, cookbooks, roles, and other Chef objects
 - **Chef InSpec**: Latest release candidate of InSpec, enabling compliance and security testing.
 
 ### Testing and quality assurance

content/install.md

@@ -16,7 +16,7 @@ draft = false
 
 Chef Workstation has the following requirements:
 
-- Linux x86-64 (64-bit) systems only
+- Linux and Windows x86-64 (64-bit) systems only
 - Chef Habitat 1.6.0 or later installed
 - Minimum 2GB available disk space for installation
 - Internet connectivity for package downloads (or access to internal Habitat Builder)
@@ -178,7 +178,7 @@ The following table provides examples of common tool invocations using the Habit
 | Chef Vault        | hab pkg exec chef/chef-vault chef-vault                    | chef-vault -v         |
 | Fauxhai           | hab pkg exec chef/fauxhai fauxhai                          | fauxhai -v            |
 | Chef InSpec       | hab pkg exec chef/inspec inspec                            | inspec version        |
-| Knife             | hab pkg exec chef/knife knife                              | knife -v              |
+| knife             | hab pkg exec chef/knife knife                              | knife -v              |
 
 ## Install Chef Workstation tools
 

content/license.md

@@ -14,7 +14,7 @@ This page describes licensing requirements and how to configure a license for Ch
 
 Different Chef Workstation components have different licensing requirements:
 
-- **Knife 19**: Requires a license for bootstrapping Chef Infra Client 18 and earlier
+- **knife 19**: Requires a license for bootstrapping Chef Infra Client 18 and earlier
 - **Test Kitchen Enterprise**: Uses a license to execute tests but doesn't enforce licensing
 
 ## Get a license
@@ -28,7 +28,7 @@ For more information, see Chef's licensing documentation [Chef licensing documen
 
 ## Add a license to Workstation
 
-If you've set a license for Chef Workstation, Test Kitchen Enterprise and Knife 19 automatically read and use it to execute tests or during bootstrap operations.
+If you've set a license for Chef Workstation, Test Kitchen Enterprise and knife 19 automatically read and use it to execute tests or during bootstrap operations.
 
 You can apply a license to Chef Workstation in two ways:
 
@@ -137,24 +137,24 @@ To display details of all licenses stored on disk:
 kitchen license list
 ```
 
-## Add a license to Knife
+## Add a license to knife
 
-Knife requires a license for bootstrapping Chef Infra Client 18 and earlier.
+knife requires a license for bootstrapping Chef Infra Client 18 and earlier.
 Chef Infra Client 19 and above doesn't require a license because it's distributed through pre-signed URLs.
 
-### How Knife uses licenses
+### How knife uses licenses
 
-During bootstrap operations, Knife transfers the license to the target node and adds it as an argument to Chef Infra Client.
+During bootstrap operations, knife transfers the license to the target node and adds it as an argument to Chef Infra Client.
 Chef Infra Client validates the license and saves it on the provisioned node for future use.
 
 ### Add a license
 
-Knife automatically reads a license that's configured locally for Chef Workstation through:
+knife automatically reads a license that's configured locally for Chef Workstation through:
 
 - The `~/.chef/licenses.yml` file
 - The `CHEF_LICENSE_KEY` environment variable
 
-You can also configure a license specifically for Knife with:
+You can also configure a license specifically for knife with:
 
 - The `knife license` CLI command
 - The `--chef-license-key` command line option
@@ -173,9 +173,9 @@ To add a license using the `knife license` CLI:
 
 1. Enter your license key at the second prompt.
 
-Knife validates the license and saves it to disk.
+knife validates the license and saves it to disk.
 
-##### Verify your Knife license
+##### Verify your knife license
 
 To verify that a valid license is saved on disk:
 

content/tools/chef_vault.md

@@ -52,7 +52,7 @@ knife[:vault_admins] = [ 'example-alice', 'example-bob', 'example-carol' ]
 
 You can override these values in the command line by using `-A`.
 
-## Knife Vault CLI
+## knife vault CLI
 
 ### Syntax
 
@@ -699,7 +699,7 @@ A JSON file can be used in place of specifying the values on the command line, s
 
   Sub-commands: `refresh`, `remove`, `rotate`
 
-### Knife bootstrap options
+### knife bootstrap options
 
 Use the following options with a validatorless bootstrap to specify items that are stored in Chef Vault:
 

content/tools/ctl_chef.md

@@ -12,7 +12,7 @@ draft = false
 <!-- markdownlint-disable-file MD024 MD036-->
 <!-- vale chef.policyfile = NO -->
 
-The chef executable is a command-line tool that does the following:
+The `chef` executable is a command-line tool that does the following:
 
 - Generates repositories, cookbooks, recipes, attributes, templates, and custom resources.
 - Installs gems into the Chef development environment's Ruby installation.

content/tools/knife/_index.md

@@ -1,11 +1,11 @@
 +++
-title = "About Knife"
+title = "About knife"
 draft = false
 
 [menu]
   [menu.tools]
-    title = "About Knife"
-    identifier = "tools/knife/knife.md About Knife"
+    title = "About knife"
+    identifier = "tools/knife/knife.md About knife"
     parent = "tools/knife"
     weight = 10
 +++
@@ -22,23 +22,23 @@ chef-repo and Chef Infra Server. knife helps users to manage:
 - The installation of Chef Infra Client onto nodes
 - Searching of indexed data on Chef Infra Server
 
-## Configure Knife
+## Configure knife
 
-See the following guides to setup and configure Knife:
+See the following guides to setup and configure knife:
 
-- **[Set up Knife](/tools/knife/knife_setup/)**: Configure knife to interact with your organization's Chef Infra Server and infrastructure.
-- **[Knife Common Options](/tools/knife/common_options/)**: Common options that are available for all knife subcommands.
+- **[Set up knife](/tools/knife/set_up/)**: Configure knife to interact with your organization's Chef Infra Server and infrastructure.
+- **[knife Common Options](/tools/knife/common_options/)**: Common options that are available for all knife subcommands.
 - **[config.rb](/tools/knife/config_rb/)**: Common options for the `config.rb` file
 - **[config.rb optional settings](tools/knife/config_rb_optional_settings/)**: Additional options for your `config.rb` file
 
-## Knife subcommands
+## knife subcommands
 
 knife includes a collection of built in subcommands that work together
 to provide the functionality required to take specific actions
 against any object in an organization, including cookbooks, nodes,
 roles, data bags, environments, and users.
 
-### Knife command syntax
+### knife command syntax
 
 All knife subcommands have the following syntax:
 
@@ -161,16 +161,16 @@ to return:
 aardvarks/ anagrams/
 ```
 
-## Knife Plug-ins
+## knife Plug-ins
 
-Knife functionality can be extended with plugins, which work the same as
-built-in subcommands (including common options). Knife plugins have been
+knife functionality can be extended with plugins, which work the same as
+built-in subcommands (including common options). knife plugins have been
 written to interact with common cloud providers, to simplify common Chef
 tasks, and to aid in Chef workflows.
 
 ### Plugin Installation
 
-Knife plugins ship as RubyGems and are installed into the Chef
+knife plugins ship as RubyGems and are installed into the Chef
 Workstation installation using the `chef` command:
 
 ```bash
@@ -184,7 +184,7 @@ commands by running:
 knife rehash
 ```
 
-### Chef Maintained Knife Plugins
+### Chef Maintained knife Plugins
 
 Chef maintains the following plugins which ship with Chef Workstation:
 
@@ -200,6 +200,6 @@ Chef maintains the following plugins which ship with Chef Workstation:
 - `knife-vcenter`
 - `knife-windows`
 
-### Community Knife Plugins
+### Community knife Plugins
 
-Knife plugins written by Chef community members can be found on Supermarket under [Knife Plugins](https://supermarket.chef.io/tools?type=knife_plugin).
+knife plugins written by Chef community members can be found on Supermarket under [knife Plugins](https://supermarket.chef.io/tools?type=knife_plugin).

content/tools/knife/common_options.md

@@ -1,11 +1,11 @@
 +++
-title = "Knife common options"
+title = "knife common options"
 draft = false
 
 [menu]
   [menu.tools]
-    title = "Knife common options"
-    identifier = "tools/knife/common_options.md Knife Common Options"
+    title = "knife common options"
+    identifier = "tools/knife/common_options.md knife Common Options"
     parent = "tools/knife"
     weight = 110
 +++

content/tools/knife/config_rb.md

@@ -1,12 +1,12 @@
 +++
-title = "Configure Knife"
+title = "Configure knife"
 draft = false
 
 
 
 [menu]
   [menu.tools]
-    title = "Configure Knife"
+    title = "Configure knife"
     identifier = "tools/knife/config_rb.md config.rb (knife.rb)"
     parent = "tools/knife"
     weight = 40

content/tools/knife/config_rb_optional_settings.md

@@ -1,5 +1,5 @@
 +++
-title = "Optional Knife settings"
+title = "Optional knife settings"
 draft = false
 
 [menu]

content/tools/knife/install.md

@@ -1,5 +1,5 @@
 +++
-title = "Install Knife"
+title = "Install knife"
 
 [menu.workstation]
 title = "Install"
@@ -8,32 +8,32 @@ parent = "workstation/knife"
 weight = 20
 +++
 
-Knife is included as a component of Chef Workstation, but you can also install it as a standalone package.
-The Knife standalone installation doesn't include the Knife cloud provider plugins (knife-ec2, knife-google, knife-windows).
-For that reason, Progress Chef recommends installing Chef Workstation, which includes Knife and the Knife cloud provider plugins.
+knife is included as a component of Chef Workstation, but you can also install it as a standalone package.
+The knife standalone installation doesn't include the knife cloud provider plugins (knife-ec2, knife-google, knife-windows).
+For that reason, Progress Chef recommends installing Chef Workstation, which includes knife and the knife cloud provider plugins.
 
-If you want to install Knife as a standalone component, follow the steps below.
+If you want to install knife as a standalone component, follow the steps below.
 
 ## Requirements
 
-Knife has the following requirements:
+knife has the following requirements:
 
 - Supported on Linux (Ubuntu 18.04+, CentOS 7+, RHEL 7+), macOS 10.15+, or Windows 10/Server 2016+
 - Chef Habitat 1.6.0 or later installed
 - Internet connectivity for package download and bootstrapping remote nodes
 - SSH or WinRM to manage remote nodes
 
-## Install the Knife standalone package
+## Install the knife standalone package
 
-To install the Knife standalone package, follow these steps:
+To install the knife standalone package, follow these steps:
 
-1. Install Knife:
+1. Install knife:
 
     ```sh
     hab pkg install chef/knife --channel unstable --binlink --force
     ```
 
-1. Optional: After installation, verify Knife is installed and working:
+1. Optional: After installation, verify knife is installed and working:
 
     ```sh
     knife --version