Update licensing information at _index.md (#153) (#155)

* Update licensing information at _index.md

Licensing information for Infra Client 19 was out-of-date. Have made the changes.

* Editing license text



---------



(cherry picked from commit fa875e8)

Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
Co-authored-by: Chef-Pradyumn <prabhu@progress.com>
Co-authored-by: Ian Maddaus <ian.maddaus@progress.com>

Author: 3 people

content/license/_index.md

@@ -9,45 +9,43 @@ parent = "licensing"
 weight = 11
 +++
 
-This document outlines the licensing requirements and enforcement policies for Chef Infra Client 19.
+This document outlines the licensing requirements and enforcement policies for Chef Infra Client.
 
 Depending on the distribution you download and install, you may have to add a license key to run Chef Infra Client.
-You must also [accept the Chef End User License Agreement (Chef EULA)](#accept-the-end-user-license-agreement) when you first run Chef Infra Client 19.
+You must also [accept the Chef End User License Agreement (Chef EULA)](#accept-the-end-user-license-agreement) when you first run Chef Infra Client.
 
 ## Licensing requirements
 
-Chef Infra Client 19 has different licensing requirements depending on the distribution you download.
+Chef Infra Client has different licensing requirements depending on the distribution you download.
 
-### No license enforcement
-
-Chef Infra Client doesn't require a license to run if you download an official distribution.
+### License required
 
-This includes:
+License key requirements are enforced:
 
-- Downloading Infra Client from the customer portal.
-- Installing the Infra Client Habitat package.
-- Installing Infra Client using the migration tool or native installer.
+- At the point of download for the binaries from Progress Chef Download Portal or through Habitat package distribution.
+- At first run when using runtime installations and workflows, if the binaries are from the Chef API.
+- For Chef software from any other sources not listed above, such as public Ruby gems or channels outside of the official Habitat distribution and download portal.
 
-### License required
+### No license key requirement
 
-You need a license key to run Chef Infra Client when you:
+Chef Infra Client doesn't require a license key to:
 
-- Download it from unofficial sources (public Ruby gem).
-- Use runtime installations and workflows.
+- Use runtime installations and workflows when using your own source to download binaries.
+- Execute any non-download commands using software obtained from an official source.
 
 ## Add a license
 
 Chef Infra Client has three ways to set a license:
 
-- with an environment variable
-- with a command line option
-- with the command line interactive dialog
+- An environment variable
+- A command line option
+- The command line interactive dialog
 
 After setting a license key, Chef Infra Client validates it with Progress Chef's licensing service.
 
 ### Environment variable
 
-- You can set the license key adding the `CHEF_LICENSE_KEY` environment variable:
+- You can set the license key by setting the `CHEF_LICENSE_KEY` environment variable:
 
   ```sh
   export CHEF_LICENSE_KEY=<LICENSE_KEY>
@@ -75,13 +73,14 @@ To set a license key with the CLI interactive dialog, follow these steps:
 
     It should return version 19.0.54 or greater for Infra Client RC 1.
 
-1. Run `chef-client` in local mode and why-run mode:
+1. Run `chef-client` in local mode and `why-run` mode:
 
     ```sh
     chef-client --local-mode --why-run
     ```
 
-    Local mode runs Chef Infra Client on your local machine as if it were running against Chef Infra Server. why-run mode shows you what Chef Infra Client would configure if a Chef Infra Client run occurs.
+    Local mode runs Chef Infra Client on your local machine as if it were running against Chef Infra Server.
+    `why-run` mode shows you what Chef Infra Client would configure during a Chef Infra Client run.
 
 1. At the first prompt, select **I already have a license ID**.
 
@@ -103,7 +102,7 @@ To set a license key with the CLI interactive dialog, follow these steps:
 
 ## Accept the End User License Agreement
 
-When you first run Chef Infra Client 19, you must accept the End User License Agreement (EULA).
+When you first run Chef Infra Client, you must accept the End User License Agreement (EULA).
 
 Chef Infra Client accepts a license using a command line option, environment variable, or config file.
 
@@ -118,19 +117,19 @@ Chef Infra Client accepts the following license acceptance options:
 : Similar to `accept`, but no messaging is sent to STDOUT.
 
 `accept-no-persist`
-: Similar to `accept-silent`, but no marker file is persisted. Future invocation will require accepting the license again.
+: Similar to `accept-silent`, but no marker file is persisted. Future invocations will require accepting the license again.
 
 ### Command line option
 
-Accept the Chef License with a command line invocation.
+To accept the Chef License, run `chef-client` with the `--chef-license` option:
 
 ```sh
 chef-client --chef-license <LICENSE_OPTION>
 ```
 
 ### Environment variable
 
-Accept the Chef License by setting an environment variable. For example:
+To accept the Chef License, set the `CHEF_LICENSE` environment variable:
 
 ```sh
 export CHEF_LICENSE="<LICENSE_OPTION>"
@@ -139,9 +138,10 @@ chef-client OPTION VALUE
 
 ### Config file
 
-You can accept the Chef License with the Chef Infra Client or Knife config files.
+You can accept the Chef License in the Chef Infra Client or Knife config files.
 
-On a workstation, you can set this in the [`~/.chef/config.rb` or `~/.chef/knife.rb` files](https://docs.chef.io/workstation/config_rb/), and on a node you can set this in the [`/etc/chef/client.rb`]({{< relref "/install/config_rb_client" >}}) file.
+On a workstation, set this in the [`~/.chef/config.rb` or `~/.chef/knife.rb` files](https://docs.chef.io/workstation/config_rb/).
+On a node, set this in the [`/etc/chef/client.rb`]({{< relref "/install/config_rb_client" >}}) file.
 
 ```ruby
 chef_license "<LICENSE_OPTION>"