[TAAP-2969] Style edits

Author: RichardJJG

tap-gui/plugins/app-live-view-springcloudgateway.hbs.md

@@ -33,16 +33,16 @@ option from the **Information Category** drop-down menu.
 
 The API Authentications By Path page displays the total requests, number of successes, and forbidden
 and unsuccessful authentications grouped by the HTTP method and gateway route path.
-The page also displays the success rate for each of the routes.
+The page also displays the success rate for each route.
 
 ![API Authentications By Path Page in the UI. The table gives information including numbers for requests, successes, and forbidden errors.](images/api-authentications-by-path.png)
 
 > **Note** In addition to the preceding three pages, the Spring Boot actuator pages are also displayed.
 
 ## <a id="troubleshooting"></a> Troubleshooting
 
-You might run into cases where a workload running on your cluster does not show up in the
-Application Live View overview, or the detail pages do not load any information while running,
-or other similar issues.
-For more information, see [Troubleshooting](../../app-live-view/troubleshooting.md) in the
-Application Live View documentation.
+You might run into cases where a workload running on your cluster does not appear in the Application
+Live View overview, or the detail pages do not load any information while running, or other similar
+issues.
+For more information about such issues, see [Troubleshooting](../../app-live-view/troubleshooting.hbs.md)
+in the Application Live View documentation.

tap-gui/plugins/app-live-view-steeltoe.hbs.md

@@ -33,7 +33,7 @@ menu.
 The health page provides detailed information about the health of the application.
 It lists all the components that make up the health of the application, such as readiness, liveness,
 and disk space.
-It displays the status and details associated with each of the components.
+It displays the status and details associated with each component.
 
 ![Health Page in the UI showing information such as readiness, disk space, and liveness.](images/health-steeltoe.png)
 
@@ -44,30 +44,30 @@ To access the **Environment** page, select the **Environment** option from the
 
 The Environment page contains details of the applications' environment.
 It contains properties including, but not limited to, system properties, environment variables, and
-configuration properties (such as appsettings.json) in a Steeltoe application.
+configuration properties (such as `appsettings.json`) in a Steeltoe application.
 
 The page includes the following capabilities for `viewing` configured environment properties:
 
-- The UI has a search feature that enables the user to search for a property or values.
-- Each property has a search icon at the right corner which helps the user quickly see all the
+- The UI has a search feature that enables you to search for a property or values.
+- Each property has a search icon at the right corner which helps you quickly see all the
   occurrences of a specific property key without manually typing in the search box.
   Clicking the search button locates the property name.
 - The **Refresh Scope** button on the top right corner of the page probes the application to refresh
   all the environment properties.
 
 The page also includes the following capabilities for `editing` configured environment properties:
 
-- The UI allows the user to edit environment properties and see the live changes in the application.
+- The UI allows you to edit environment properties and see the live changes in the application.
   These edits are temporary and go away if the underlying pod is restarted.
-- For each of the configured environment properties, the user can edit its value by clicking on the
+- For each of the configured environment properties, you can edit its value by clicking on the
   **Override** button in the same row.
-  After the value is saved, the user can view the message that the property was overridden from the
+  After the value is saved, you can view the message that the property was overridden from the
   initial value. Also, the updated property is visible in the **Applied Overrides** section at the
   top of the page.
   The **Reset** button in the same row resets the environment property to the initial state.
-- The user can also edit or remove the overridden environment variables in the **Applied Overrides**
+- You can also edit or remove the overridden environment variables in the **Applied Overrides**
   section.
-- The **Applied Overrides** section also enables the user to add new environment properties to the
+- The **Applied Overrides** section also enables you to add new environment properties to the
   application.
 
 > **Note** The `management.endpoint.env.post.enabled=true` must be set in the application config
@@ -94,7 +94,7 @@ Use the **Changes Only** toggle to display the changed log levels.
 Use the search feature to search by logger name.
 Click **Reset All** to reset all the loggers to the default state.
 
-> **Note** The UI allows the user to change the log levels and see the live changes on the application.
+> **Note** The UI allows you to change the log levels and see the live changes on the application.
 > These changes are temporary and go away if the underlying pod is restarted.
 
 ![Screenshot of the Log Levels page. The log level WARN is selected for every logger except Default.](images/log-levels-steeltoe.png)
@@ -135,12 +135,12 @@ To access the **Request Mappings** page, select the **Request Mappings** option
 
 This page provides information about the application’s request mappings.
 For each mapping, the page displays the request handler method.
-The user can view more details of the request mapping, such as the header metadata of the application.
+You can view more details of the request mapping, such as the header metadata of the application.
 
-When a user clicks on the request mapping, a side panel appears.
+When you click on the request mapping, a side panel appears.
 This panel contains information about the mapping-media types `Produces` and `Consumes`.
 The panel also displays the `Handler` class for the request.
-The search feature enables the user to search for the request mapping or the method.
+The search feature enables you to search for the request mapping or the method.
 The toggle **/actuator/\*\* Request Mappings** displays the actuator-related mappings of the
 application.
 
@@ -155,13 +155,13 @@ The **HTTP Requests** page provides information about HTTP request-response exch
 application.
 
 The graph visualizes the requests per second, which indicates the response status of all the requests.
-The user can filter by the response statuses, which include **info**, **success**, **redirects**,
+You can filter by the response statuses, which include **info**, **success**, **redirects**,
 **client-errors**, and **server-errors**.
 The trace data is captured in detail in a tabular format with metrics, such as **timestamp**,
 **method**, **path**, **status**, **content-type**, **length**, and **time**.
 
 The search feature on the table filters the traces based on the search text box value.
-By clicking on the timestamp, the user can view more details of the request, such as method, headers,
+By clicking on the timestamp, you can view more details of the request, such as method, headers,
 and the response of the application.
 
 The refresh icon above the graph loads the latest traces of the application.
@@ -203,7 +203,7 @@ You can choose from a list of actuator endpoints and parse through the raw actua
 
 ## <a id="troubleshooting"></a> Troubleshooting
 
-You might run into cases where a workload running on your cluster does not show up in the
+You might run into cases where a workload running on your cluster does not appear in the
 Application Live View overview, or the Details pages do not load any information while running, or
 other similar issues.
 For help with troubleshooting common issues, see [Troubleshooting](../../app-live-view/troubleshooting.hbs.md).

tap-gui/plugins/application-accelerator.hbs.md

@@ -80,4 +80,4 @@ To develop your code:
 ## <a id='next-steps'></a>Next steps
 
 To learn more about Application Accelerator for VMware Tanzu, see the
-[Application Accelerator documentation](../../application-accelerator/about-application-accelerator.md).
+[Application Accelerator documentation](../../application-accelerator/about-application-accelerator.hbs.md).

tap-gui/plugins/runtime-resource-visibility.hbs.md

@@ -9,9 +9,9 @@ associated with their workloads.
 
 Do one of the following actions to access the Runtime Resources Visibility plug-in:
 
-- [Install the Tanzu Application Platform Full or View profile](../../install-intro.md)
-- [Install Tanzu Application Platform without using a profile](../../install-intro.md) and then
-  install [Tanzu Developer Portal separately](../install-tap-gui.md)
+- [Install the Tanzu Application Platform Full or View profile](../../install-intro.hbs.md)
+- [Install Tanzu Application Platform without using a profile](../../install-intro.hbs.md) and then
+  install [Tanzu Developer Portal separately](../install-tap-gui.hbs.md)
 - Review the section [If you have a metrics server](#metrics-server)
 
 ## <a id="metrics-server"></a> If you have a metrics server
@@ -45,28 +45,28 @@ Where:
 
 You can retrieve this secret's ID by running:
 
-```kubectl
+```console
 kubectl get secrets -n tap-gui
 ```
 
 and then running
 
-```kubectl
+```console
 kubectl describe secret tap-gui-token-ID
 ```
 
-Where ID is the secret name from the first step.
+Where `ID` is the secret name from the first step.
 
 > **Caution** If you enable metrics for a cluster but do not have a metrics server running on it,
 > Tanzu Application Platform web interface users see an error notifying them that there is a
 > problem connecting to the back end.
 
 ## <a id="Visualize-app"></a> Visualize Workloads on Tanzu Developer Portal
 
-In order to view your applications on Tanzu Developer Portal, use the following steps:
+To view your applications on Tanzu Developer Portal, use the following steps:
 
-1. [Deploy your first application on the Tanzu Application Platform](../../getting-started/deploy-first-app.md)
-1. [Add your application to Tanzu Developer Portal Software Catalog](../../getting-started/deploy-first-app.md#add-app-to-gui-cat)
+1. [Deploy your first application on the Tanzu Application Platform](../../getting-started/deploy-first-app.hbs.md)
+1. [Add your application to Tanzu Developer Portal Software Catalog](../../getting-started/deploy-first-app.hbs.md#add-app-to-gui-cat)
 
 ## <a id="nav-rr-vis-screen"></a> Navigate to the **Runtime Resources Visibility** screen
 
@@ -101,7 +101,7 @@ Supply Chain, including:
 - Knative Services, Configurations, Revisions, and Routes
 
 For more information, see
-[Supply Chain Choreographer in Tanzu Developer Portal](scc-tap-gui.md).
+[Supply Chain Choreographer in Tanzu Developer Portal](scc-tap-gui.hbs.md).
 
 CRDs from Supply Chain are associated with Knative Resources, further down the chain, and built-in
 resources even further down the chain.
@@ -132,8 +132,8 @@ The following are some attributes that are displayed in the overview card:
 
 ![Screenshot of an Overview card. The VIEW POD LOGS and VIEW dot YAML buttons are at the top-right.](images/runtime-resources-overview.png)
 
->**Note** The **VIEW CPU AND MEMORY DETAILS** and **VIEW THREADS** sections are only available for
-applications supporting Application Live View.
+> **Note** The **VIEW CPU AND MEMORY DETAILS** and **VIEW THREADS** sections are only available for
+> applications supporting Application Live View.
 
 ### <a id="status-card"></a>Status card
 
@@ -187,7 +187,7 @@ user-configured resource limits on the pod, defined in accordance with the
 
 For applications built using Spring Boot, you can also monitor the actual
 real-time resource use using
-[Screenshot of Application Live View for Spring Boot Applications in Tanzu Developer Portal.](app-live-view-springboot.md).
+[Screenshot of Application Live View for Spring Boot Applications in Tanzu Developer Portal.](app-live-view-springboot.hbs.md).
 
 Metrics and limits are also displayed for each container on a pod details page.
 If a particular container's current limit conflicts with a namespace-level
@@ -215,7 +215,7 @@ Kubernetes manages these resource units by using a binary base, which is explain
 ## <a id="pod-details"></a>Navigating to Application Live View
 
 To view additional information about your running applications, see the
-[Application Live View](app-live-view-springboot.md) section in the **Pod Details** page.
+[Application Live View](app-live-view-springboot.hbs.md) section in the **Pod Details** page.
 
 ![Screenshot of Tanzu Java web app runtime resource detail page.](images/runtime-resources-pod-details.png)
 
@@ -251,7 +251,7 @@ For optimal performance, the pod logs page limits the total log entries displaye
 
 ### <a id="changing-log-levels"></a>Changing log levels
 
-If the pod is associated with an application that supports [Application Live View](app-live-view.md),
+If the pod is associated with an application that supports [Application Live View](app-live-view.hbs.md),
 you can change the application's log levels by clicking the **Change Log Levels** button.
 You then see a panel that enables you to select levels for each logger associated with your application.
 

tap-gui/plugins/sa-tap-gui.hbs.md

@@ -50,7 +50,7 @@ The sum of a workload's CVEs might not match the
 The data on this dashboard is based on `kubectl describe` for `SourceScan` and `ImageScan`.
 The data on the Supply Chain Choreographer's Vulnerability Scan Results is based on Metadata Store data.
 
-Only vulnerability scans associated to a Cartographer workload appear.
+Only vulnerability scans associated with a Cartographer workload appear.
 Use [tanzu insight](../../cli-plugins/insight/cli-overview.hbs.md) to view results for
 non-workload scan results.
 

tap-gui/plugins/scc-tap-gui.hbs.md

@@ -35,8 +35,8 @@ Tanzu Developer Portal has automation for enabling connection between Tanzu Deve
 no configuration.
 
 > **Important** There is a known issue with the automatic configuration breaking the SBOM download
-> feature introduced in Tanzu Application Platform v1.6. Please update `tap-values.yaml` as described
-> in [Troubleshooting](../../tap-gui/troubleshooting.hbs.md#sbom-not-working).
+> feature introduced in Tanzu Application Platform v1.6. To fix this issue, edit `tap-values.yaml` as
+> described in [Troubleshooting](../../tap-gui/troubleshooting.hbs.md#sbom-not-working).
 
 To deactivate this automation, add the following block to the Tanzu Developer Portal section within
 `tap-values.yaml`:
@@ -104,7 +104,7 @@ tap_gui:
         target: SOMETHING
 ```
 
-### <a id="scan-manual"></a> Manually connect Tanzu Developer Portal to Metadata Store
+### <a id="scan-manual"></a> Manually connect Tanzu Developer Portal to the Metadata Store
 
 To manually enable CVE scan results:
 
@@ -140,7 +140,8 @@ For more information, see [GitOps vs. RegistryOps](../../scc/gitops-vs-regops.hb
 
 ## <a id="sc-visibility"></a> Supply Chain Visibility
 
-Before using the SCC plug-in to visualize a workload, you must create a workload.
+Before using the Supply Chain Visibility (SCC) plug-in to visualize a workload, you must create a
+workload.
 
 The workload must have the `app.kubernetes.io/part-of` label specified, whether you manually create
 the workload or use one supplied with the OOTB supply chains.
@@ -661,7 +662,7 @@ To define a new `ClusterTemplate`:
    For example:
 
    ```console
-   kubectl get ClusterTemplates config-writer-template -n my-apps -oyaml >> ~/cluster-template.yaml
+   $ kubectl get ClusterTemplates config-writer-template -n my-apps -oyaml >> ~/cluster-template.yaml
    ```
 
 3. Verify that the file, when cleaned up, looks similar to the following: