fix nits

Author: rosemarymarano

documentation/1.0/content/developer/_index.md

@@ -8,25 +8,25 @@ pre = "<b> </b>"
 The WebLogic Kubernetes Toolkit UI is a desktop application designed to help WebLogic users move their applications to run in a Kubernetes environment.
 
 ### Setting up your development environment
-1. Download and install the latest LTS version of node.js from [https://nodejs.org/en/download/](https://nodejs.org/en/download/).
-2. If you rely on a proxy server to reach the Internet, set these 5 environment variables to configure the proxy correctly:
+1. Download and install the latest LTS version of `node.js` from [https://nodejs.org/en/download/](https://nodejs.org/en/download/).
+1. If you rely on a proxy server to reach the Internet, set these five environment variables to configure the proxy correctly:
    ```
    ELECTRON_GET_USE_PROXY=true
    GLOBAL_AGENT_HTTPS_PROXY=<proxy-url>
    WKTUI_DEV_PROXY=<proxy-url>
    HTTPS_PROXY=<proxy-url>
    NO_PROXY=<list-of-no-proxy-hosts>
    ```
-3. Open a command line window are run the following command to update the version of npm to the latest:
+1. Open a command line and run the following command to update the version of `npm` to the latest:
    ```bash
    sudo npm install --global npm
    ```
-   Note: If developing on Windows, run the following commands from a shell running as Administrator instead:
+   **Note**: If developing on Windows, run the following commands from a shell running as Administrator instead:
    ```cmd
    npm install --global --production npm-windows-upgrade
    npm-windows-upgrade --npm-version latest
    ```
-4. Set up your global git configuration by running the following commands:
+1. Set up your global git configuration by running the following commands:
    ```bash
    git config --global user.name "<your real name>"
    git config --global user.email "<your-oracle-email-address>"
@@ -35,19 +35,19 @@ The WebLogic Kubernetes Toolkit UI is a desktop application designed to help Web
    **This last command is critical if you are developing on either Windows or MacOS.  Yes, the MacOS file system
    is, by default, case-insensitive!**
 
-5. Clone the git repository on GitHub at [https://github.com/oracle/weblogic-toolkit-ui](https://github.com/oracle/weblogic-toolkit-ui).
-6. Open a command-line in the `weblogic-toolkit-ui` directory and run `npm install` to download and install the JavaScript dependencies required by the project.
-7. Open a command-line in the `weblogic-toolkit-ui/electron` directory and run `npm run install-tools`.
-8. Open a command-line in the `weblogic-toolkit-ui/webui` directory and run `npm start`.
-9. Once the server from the previous step is fully running, open a command-line in the `weblogic-toolkit-ui/electron` directory and run `npm start`.
+1. Clone the git repository on GitHub at [https://github.com/oracle/weblogic-toolkit-ui](https://github.com/oracle/weblogic-toolkit-ui).
+1. Open a command line in the `weblogic-toolkit-ui` directory and run `npm install` to download and install the JavaScript dependencies required by the project.
+1. Open a command line in the `weblogic-toolkit-ui/electron` directory and run `npm run install-tools`.
+1. Open a command line in the `weblogic-toolkit-ui/webui` directory and run `npm start`.
+1. After the server from the previous step is fully running, open a command line in the `weblogic-toolkit-ui/electron` directory and run `npm start`.
 
 ### Building a Windows or MacOS installer
-0. Set up your development environment and verify that the application is working properly from it.
-1. Open a command-line in the `weblogic-toolkit-ui/electron` directory and run `npm run build`.
-2. Find the executable and installer(s) in the `weblogic-toolkit-ui/dist` directory.
+1. Set up your development environment and verify that the application is working properly from it.
+1. Open a command line in the `weblogic-toolkit-ui/electron` directory and run `npm run build`.
+1. Find the executable and installer(s) in the `weblogic-toolkit-ui/dist` directory.
 
 ### Building a Linux installer
-0. Set up your development environment and verify that the application is working properly from it.
-1. Open a command-line in the `weblogic-toolkit-ui/webui` directory and run `npm run build:release`.
-2. From the command-line in the `weblogic-toolkit-ui/scripts` directory, run `./devBuildLinuxInstallers.sh`.
-3. Find the executable and installer(s) in the `weblogic-toolkit-ui/dist` directory.
+1. Set up your development environment and verify that the application is working properly from it.
+1. Open a command line in the `weblogic-toolkit-ui/webui` directory and run `npm run build:release`.
+1. From the command line in the `weblogic-toolkit-ui/scripts` directory, run `./devBuildLinuxInstallers.sh`.
+1. Find the executable and installer(s) in the `weblogic-toolkit-ui/dist` directory.

documentation/1.0/content/navigate/image.md

@@ -185,10 +185,10 @@ the `Create Image` button on the `Image` page or the `Go` menu.
 At a high level, `Create Image` performs the following steps:
 
 1. Validates the input values necessary for running the action based on your selections.
-2. Saves the WKT Project, if needed.
-3. Adds the installers to the WIT cache on the local machine using the WebLogic Image Tool
+1. Saves the WKT Project, if needed.
+1. Adds the installers to the WIT cache on the local machine using the WebLogic Image Tool
    [Cache](https://oracle.github.io/weblogic-image-tool/userguide/tools/cache/) command.
-4. Builds the image on the local machine using the WebLogic Image Tool
+1. Builds the image on the local machine using the WebLogic Image Tool
    [Create](https://oracle.github.io/weblogic-image-tool/userguide/tools/create-image/) command.
 
 ### Push Image
@@ -200,6 +200,6 @@ At a high level, `Push Image` performs the following steps:
 
 1. Validates the input values necessary for running the action based on your selections.  This includes making
    sure that an image with the specified `Image Tag` value exists in the local machine's image cache.
-2. Saves the WKT Project, if needed.
-3. Logs in to the container image registry, if specified.
-4. Pushes the image to the container image registry.
+1. Saves the WKT Project, if needed.
+1. Logs in to the container image registry, if specified.
+1. Pushes the image to the container image registry.

documentation/1.0/content/navigate/kubernetes/_index.md

@@ -10,9 +10,9 @@ Kubernetes cluster where the WebLogic domain will be managed by the WebLogic Kub
 to help you:
 
 1. [Configure]({{< relref "/navigate/kubernetes/k8s-client-config#client-configuration" >}})  your Kubernetes client (`kubectl`) to connect to the Kubernetes cluster.
-2. [Install]({{< relref "/navigate/kubernetes/k8s-wko#install-operator" >}}) the WebLogic Kubernetes Operator.
-3. [Deploy]({{< relref "/navigate/kubernetes/k8s-weblogic-domain#deploy-domain" >}}) the WebLogic domain's `Domain` resource configuration used by WebLogic Kubernetes Operator.
-4. [Install]({{< relref "/navigate/kubernetes/k8s-ingress-controller#install-ingress-controller" >}}) an ingress controller, if needed, and add ingress routes to allow access to the WebLogic domain from
+1. [Install]({{< relref "/navigate/kubernetes/k8s-wko#install-operator" >}}) the WebLogic Kubernetes Operator.
+1. [Deploy]({{< relref "/navigate/kubernetes/k8s-weblogic-domain#deploy-domain" >}}) the WebLogic domain's `Domain` resource configuration used by WebLogic Kubernetes Operator.
+1. [Install]({{< relref "/navigate/kubernetes/k8s-ingress-controller#install-ingress-controller" >}}) an ingress controller, if needed, and add ingress routes to allow access to the WebLogic domain from
    outside the Kubernetes cluster.
 
 {{% children style="h4" description="true" %}}

documentation/1.0/content/navigate/kubernetes/k8s-ingress-controller.md

@@ -21,7 +21,7 @@ This section supports two distinct functions related to an ingress controller.
 controller to a Kubernetes cluster.  Second, it supports adding the necessary routes to an ingress controller to make
 a deployed WebLogic domain's endpoints accessible.
 
-#### Design View
+### Design View
 `Design View` helps you specify the data needed to install an ingress controller, if desired, and
 specify the data needed to expose one or more endpoints for a deployed WebLogic domain.  This page contains three panes:
 

documentation/1.0/content/navigate/kubernetes/k8s-wko.md

@@ -171,9 +171,9 @@ to the image registry specified by its image tag.  You can access it by using th
 At a high level, `Push Image` performs the following steps:
 
 1. Validates the input values necessary for running the action based on your selections.
-2. Saves the WKT Project, if needed.
-3. Creates the Kubernetes namespace for installing the operator, if needed.
-4. Creates the Kubernetes service account for the operator to use, if needed.
-5. Creates the operator image pull secret, if needed.
-6. Adds the latest operator Helm chart to the local Helm repository.
-7. Runs Helm to install the operator using the specified configuration.
+1. Saves the WKT Project, if needed.
+1. Creates the Kubernetes namespace for installing the operator, if needed.
+1. Creates the Kubernetes service account for the operator to use, if needed.
+1. Creates the operator image pull secret, if needed.
+1. Adds the latest operator Helm chart to the local Helm repository.
+1. Runs Helm to install the operator using the specified configuration.

documentation/1.0/content/navigate/model.md

@@ -108,8 +108,8 @@ title bar and follow the prompts to choose the type of content to add and select
 For example, to add a WAR file called `todo.war` to the archive, do the following:
 
 1. On the archive editor title bar, click `+`.
-2. In the resulting dialog, choose `Application File` from the list and click `OK`.
-3. In the resulting file chooser dialog, select the `todo.war` file and click `Select`.
+1. In the resulting dialog, choose `Application File` from the list and click `OK`.
+1. In the resulting file chooser dialog, select the `todo.war` file and click `Select`.
 
 This will result in the file structure `wlsdeploy/applications/todo.war` being added to the archive editor pane.
 At this point, the application has not created or modified the archive file; it is simply storing
@@ -144,10 +144,10 @@ Image` action, though typically it is best to run `Prepare Model` explicitly, pr
 `Prepare Model` does the following:
 
 1. Removes model sections and fields that are not compatible with the target environment.
-2. Replaces endpoint values with model tokens that reference variables.
-3. Replaces credential values with model tokens that reference either a field in a Kubernetes secret or a variable.
-4. Provides default values for fields displayed in the application's variable, variable overrides, and secret editors.
-5. Extracts topology information to the application that it uses to generate the resource file used to deploy the domain.
+1. Replaces endpoint values with model tokens that reference variables.
+1. Replaces credential values with model tokens that reference either a field in a Kubernetes secret or a variable.
+1. Provides default values for fields displayed in the application's variable, variable overrides, and secret editors.
+1. Extracts topology information to the application that it uses to generate the resource file used to deploy the domain.
 
 For more information, see the WDT [model tokens](https://oracle.github.io/weblogic-deploy-tooling/concepts/model/#model-tokens)
 documentation.

documentation/1.0/content/navigate/project-settings.md

@@ -46,11 +46,11 @@ A creative person might realize that they can use the passphrase-based encryptio
 in the native OS credential store to another machine.  The steps to accomplish this would be:
 
 1. Open the project using the native OS credential store on the machine where the credentials are stored.
-2. Change the credential storage option to passphrase-based encryption and enter a passphrase.
-3. Save the project file.
-4. Open the project file on a different machine, supplying the passphrase entered in step 2.
-5. Change the credential storage option to native OS credential store.
-6. Save the project file.
+1. Change the credential storage option to passphrase-based encryption and enter a passphrase.
+1. Save the project file.
+1. Open the project file on a different machine, supplying the passphrase entered in step 2.
+1. Change the credential storage option to native OS credential store.
+1. Save the project file.
 
 The final choice, `Not Stored`, is to not store the credentials at all. While this is a viable option, it also means that whenever you
 need to run any of the actions that require credentials, you will need to re-enter the value of every credential in the

documentation/1.0/content/setup/install.md

@@ -6,7 +6,7 @@ weight: 2
 description: "Install the WKT UI application and check for updates."
 ---
 
-1. Download the latest WebLogic Kubernetes Toolkit UI (WKT UI) application installers from the [Github Releases section](https://github.com/oracle/weblogic-toolkit-ui/releases) of this repository.
+1. Download the latest WebLogic Kubernetes Toolkit UI (WKT UI) application installers from the [GitHub Releases section](https://github.com/oracle/weblogic-toolkit-ui/releases) of this repository.
 1. Simply run the appropriate installer for your operating system.
 
 Application startup detects Internet connectivity to GitHub. If it fails to connect, a `Network Configuration` dialog appears in which you can set or modify your proxy settings, test your changes, and then restart the application.  
@@ -19,8 +19,8 @@ Upon application startup, if a more recent version exists, an Application Update
 
 - `Install Now`
 - `Install on Exit`
-    - Not available on MacOS.
     - Downloads the application and installs it after you exit.
+    - Not available on MacOS.
 - `Ignore Update`
 
 At any time, you can check for application updates using `Help > Check for WKT UI Updates`.