2024 Craig User Test Edits

getting-started/installation/secure-bootstrap.markdown

@@ -41,7 +41,7 @@ settings. So after we have set-up our hub (using the standard procedure
 of `cf-agent --bootstrap $HUB_IP`) we take care of the following:
 
 * `cf-serverd` must never accept a connection from a client presenting an
-  untrusted key. [Disable automatic key trust][Masterfiles Policy Framework#trustkeysfrom]
+  untrusted key. [Disable automatic key trust][Masterfiles Policy Framework#Automatic bootstrap - Trusting keys from new hosts with trustkeysfrom]
   by providing an empty list for `default:def.trustkeysfrom`.
 
 ## Bootstrap without automatically trusting

web-ui.markdown

@@ -9,11 +9,11 @@ The challenge in engineering IT infrastructure, especially as it scales
 vertically and horizontally, is to recognize the system components, what they do
 at any given moment in time (or over time), and when and how they change state.
 
-CFEngine Enterprise's data collection service, the `cf-hub` collector, collects,
+CFEngine Enterprise's data collection service, `cf-hub`, collects,
 organizes, and stores data from every host. The data is stored primarily in a
 PostgreSQL database.
 
-CFEngine Enterprise's user interface, the Mission Portal makes that data
+CFEngine Enterprise's user interface, Mission Portal, makes that data
 available to authorized users as high level reports or alerts and notifications.
 The reports can be designed in a GUI report builder or directly with SQL
 statements passed to PostgreSQL.
@@ -27,18 +27,18 @@ The dashboard contains informative widgets that you can customize to create
 alerts. All notifications of alert state changes, e.g. from OK to not-OK, are
 stored in an event log for later inspection and analysis.
 
-### Make changes to shared dashboard
+### Make changes to a shared dashboard
 
 <img src="clone-dashboard.png" alt="Clone dashboard possibility" width="490px">
 
-Create an editable copy by clicking the button that appears when you hover over
+Create an editable copy by clicking the edit button (pencil icon) that appears when you hover over
 the dashboard's row.
 
 ### Alert widgets
 
 <img src="welcome_2nd_screen.png" alt="Enterprise UI Alerts" width="520px">
 
-Alerts can have three different severity level: low, medium and high. These are
+Alerts can have three different severity levels: low, medium and high. These are
 represented by yellow, orange and red rings respectively, along with the
 percentage of hosts alerts have triggered on. Hovering over the widget will show
 the information as text in a convenient list format.
@@ -92,16 +92,15 @@ All Events can be searched and viewed from the Event Log page.
 <img src="web-ui-mission-portal-api-view-whole-system-events-rbac.png" alt="Mission Portal - Events View whole system events RBAC page" width="380px">
 
 
-### Host count widget
+### Newly bootstrapped hosts widget
 
-The hosts count widget helps to visualize the number of hosts bootstrapped to CFEngine over time.
+The Newly bootstrapped hosts widget helps to visualize the number of hosts bootstrapped to CFEngine over time.
 
-<img src="dashboard-widget-hosts-count.png" alt="Dashboard Host count" width="412px">
+<img src="dashboard-widget-newly-bootstrapped.png" alt="Dashboard Newly bootstrapped" width="412px">
 
 ## Hosts
 
-CFEngine collects data on promise compliance, and sorts hosts according to 3
-different categories: erroneous, fully compliant, and lacking data.
+CFEngine collects data on promise compliance, and sorts hosts into two categories: 100% compliant, and not.
 
 Find out more: [Hosts][]
 

web-ui/hosts.markdown

@@ -14,7 +14,7 @@ Each host is in one of two groups: out of compliance or fully compliant.
 
 <img src="Hosts-app-overview.png" alt="Hosts app overview" width="700px">
 
-A host tree based on OS (Operating system) is present by default. Host trees map hosts based on reported classes into a hierarchy. Additional host trees can be added based on classes, which could be used to view different perspectives such as geographic location, production tier, business unit, etc.... Furthermore, Each host tree can be shared based on Mission Portal role.
+A host tree based on OS (Operating system) is present by default. Host trees map hosts based on reported classes into a hierarchy. Additional host trees can be added based on classes, which could be used to view different perspectives such as geographic location, production tier, business unit, etc. Furthermore, each host tree can be shared based on Mission Portal role.
 
 <img src="Hosts-app-custom-tree-geographic-region.png" alt="Hosts app custom tree for geographic region" width="439px">
 
@@ -33,8 +33,8 @@ Take action on a host.
 <img src="host-action-buttons.png" alt="Host action buttons" width="280px">
 
 * <img src="host-info-run-agent.png" alt="Run agent" width="50px"> :: Request an unscheduled policy run
-* <img src="host-info-collect-reports.png" alt="Collect reports" width="50px">:: Request report collection
-* <img src="host-info-get-url.png" alt="Get URL" width="50px">:: Get the URL to the specific hosts info page
+* <img src="host-info-collect-reports.png" alt="Collect reports" width="50px"> :: Request report collection
+* <img src="host-info-get-url.png" alt="Get URL" width="50px"> :: Get the URL to the specific hosts info page
 * <img src="host-info-delete-host.png" alt="Delete host" width="50px"> :: Delete the host
 
 ### Host specific data
@@ -43,7 +43,7 @@ Assign host specific _Variables_ and _Classes_.
 
 <img src="host-specific-data-variables.png" alt="Host specific data variables" width="488px">
 
-Note: When defined via host specific data variables default to the `variables` _bundle_ of the `data` _namespace_. Qualify the variable with the desired bundle and namespace to override the default. For example `my_bundle.myvaribale` to define `my_bundle.myvariable` in the `data` namespace, or `my_namesapce:my_bundle.myvariable` to define `myvariable` in the `my_bundle` bundle of the `my_namespace` namespace.
+Note: When defined via host specific data, variables default to the `variables` _bundle_ of the `data` _namespace_. Qualify the variable with the desired bundle and namespace to override the default. For example `my_bundle.myvariable` to define `my_bundle.myvariable` in the `data` namespace, or `my_namespace:my_bundle.myvariable` to define `myvariable` in the `my_bundle` bundle of the `my_namespace` namespace.
 
 <img src="host-specific-data-classes.png" alt="Host specific data classes" width="488px">