second pass

Author: rosemarymarano

documentation/1.9/content/_index.md

@@ -13,11 +13,11 @@ With the Image Tool you can:
 
 * Create a Docker image and install the requested Java and WebLogic software. And, you can create a
 WebLogic domain in the image, at the same time.
-* Create a new Docker image using an existing WebLogic domain from an existing image. The new Docker
+* Create a new Docker image using an existing WebLogic domain from an existing image. The Docker
 image can start from an existing image with a JDK and Oracle middleware installation, or can install
 the JDK and Oracle Home as part of moving the domain.
-* Create a new Docker image by applying WebLogic patches to an existing image. In addition, you can
-create a WebLogic domain if one did not exist previously, update an existing domain, or deploy an application.
+* Create a new Docker image by applying WebLogic patches to an existing image. In addition,
+ if one did not exist previously, you can create a WebLogic domain, update an existing domain, or deploy an application.
 
 For detailed information, see [Image Tool]({{< relref "/userguide/tools/_index.md" >}}).
 

documentation/1.9/content/developer/build.md

@@ -8,20 +8,20 @@ weight: 1
 
 The Image Tool installer is available for download on the [Releases](https://github.com/oracle/weblogic-image-tool/releases) page.
 If you want to build the installer from source instead of downloading it, follow these instructions:
-- Download and install JDK 8u261+
-- Download and install Maven 3.6.3+
-- Clone this repository to your local environment using one of the options under `Code` near the top of this page.
-- From inside the top-level directory of the cloned project, `weblogic-image-tool`, using Maven, execute one or
+1. Download and install JDK 8u261+
+1. Download and install Maven 3.6.3+
+1. Clone [this](https://github.com/oracle/weblogic-image-tool) repository to your local environment using one of the options under `Code` near the top of this page.
+1. From inside the top-level directory of the cloned project, `weblogic-image-tool`, using Maven, execute one or
 more of these phases:
     - `validate` - Validate the project is correct and all necessary information is available.
     - `compile`  - Compile the source code.
     - `test`     - Test the compiled source code using the JUnit5 framework.
     - `package`  - Create the installer ZIP file, `imagetool.zip`.
-    - `verify`   - Run integration tests using the JUnit5 framework (Pre-requisite: Docker installed).
+    - `verify`   - Run integration tests using the JUnit5 framework (Prerequisite: Docker installed).
     - `clean`    - Restore the source by removing any items created by `package` or another phase of the build.
 
 **Note:** Maven executes build phases sequentially, `validate`, `compile`, `test`, `package`, `verify`, such that
-running `verify` will run all of these phases from `validate` through `package` before executing `verify`.
+running `verify` will run all of these phases from `validate` through `package` before running `verify`.
 
 Because the `package` phase comes before the `verify` phase, it is not necessary to run the integration tests to create
 the Image Tool installer.  If you are making changes and want to validate those changes in your environment, you will
@@ -32,22 +32,22 @@ and `STAGING_DIR`.  The first two, Oracle Support user name and password, are us
 The third, `STAGING_DIR`, should be a local folder where WebLogic Server installers, JDK installers, and pre-downloaded
 patches can be found.  The files required in the `STAGING_DIR` depend on which tests that you want to run.
 
-Example: Run a set of integration tests (available groups are `cache`, `gate`, and `nightly`:
+**Example**: Run a set of integration tests (available groups are `cache`, `gate`, and `nightly`:
 ```shell script
 mvn verify -Dtest.groups=cache
 ```
 
-Example: Run a single integration test:
+**Example**: Run a single integration test:
 ```shell script
 mvn verify -Dtest.groups=gate,nightly -Dit.test=ITImagetool#createWlsImg
 ```
 
 Integration Test groups:
 - `cache` - Tests that build and manipulate the Image Tool cache.
 - `gate`  - A basic set of integration tests that are used to validate merge requests, including building several
-Docker image (~20 minutes)
+Docker image (~20 minutes).
 - `nightly` - The full set of integration tests building various Docker images including JRF and WLS
-installations (~2 hours)
+installations (~2 hours).
 
 **Note:** In order to run an integration test that builds an image like `createWlsImg`, you must run the `cache`
-group first in order to populate the cache with the WLS and JDK installers.
+group first to populate the cache with the WLS and JDK installers.

documentation/1.9/content/release-notes.md

@@ -1,4 +1,4 @@
 # Release Notes
 
-The upcoming change to Oracle Support's recommended patches list will require
+* The upcoming change to Oracle Support's recommended patches list will require
 WebLogic Image Tool 1.9.11 in order to use the `--recommendedPatches` or `--latestPSU` flags.

documentation/1.9/content/samples/create-image-no-internet.md

@@ -7,13 +7,12 @@ weight: 2
 
 
 In this use case, because there is no Internet access, you will need to download all the installers and
-patches, plus set up the cache.  Also, you must provide a base operating system image that has the following packages installed.
+patches, plus set up the cache.  Also, you must provide a base operating system image that has the following packages installed:
+
+* `gzip`
+* `tar`
+* `unzip`
 
-```bash
-gzip
-tar
-unzip
-```
 
 ### Steps
 
@@ -38,17 +37,17 @@ and save them in a directory of your choice, for example, `/home/acmeuser/wls-in
 
     For example, if you download patch number `27342434` for WebLogic Server version 12.2.1.3.0:
 
-  ```bash
-  imagetool cache addPatch --patchId 27342434_12.2.1.3.0 --path /home/acmeuser/cache/p27342434_122130_Generic.zip
-  ```
+   ```bash
+   imagetool cache addPatch --patchId 27342434_12.2.1.3.0 --path /home/acmeuser/cache/p27342434_122130_Generic.zip
+   ```
 
-  **Note**: Refer to the [Cache](cache.md) commands for the format of ```patchId```.
+   **Note**: Refer to the [Cache]({{< relref "/userguide/tools/cache.md" >}}) commands for the format of ```patchId```.
 
 4. Then, run the command to create the image:
 
-  ```bash
-  imagetool create --fromImage myosimg:latest --tag wls:12.2.1.3.0 --patches 27342434 --version 12.2.1.3.0
-  ```
+   ```bash
+   imagetool create --fromImage myosimg:latest --tag wls:12.2.1.3.0 --patches 27342434 --version 12.2.1.3.0
+   ```
 
 5. Occasionally, a WebLogic Server patch will require patching the OPatch binaries before applying them.  We recommend downloading the latest OPatch patch and setting up the cache.  
 

documentation/1.9/content/samples/create-image-wdt.md

@@ -1,5 +1,5 @@
 ---
-title: "Create an image with a WebLogic domain using WDT"
+title: "Create an image with a WLS domain using WDT"
 date: 2019-02-23T17:19:24-05:00
 draft: false
 weight: 4

documentation/1.9/content/samples/create-image-with-internet.md

@@ -35,7 +35,7 @@ and save them in a directory of your choice, for example, `/home/acmeuser/wls-in
 
     **Note**:  The value of the version must be a valid WebLogic Server version number. This version number is used to verify and find the correct patch file to download from Oracle Support.  The format of the version is a 5 digits tuple, separated by period.  For example,  ```12.2.1.3.0``` ```12.1.3.0.0```
 
-3. Create the image using the [Create Tool](create-image.md) commands. For example:
+3. Create the image using the [Create Tool]({{< relref "/userguide/tools/create-image.md" >}}) commands. For example:
 
   ```bash
   imagetool create --tag wls:12.2.1.3.0 --latestPSU --version 12.2.1.3.0 --user  username@mycompany.com --passwordEnv MYPWD  
@@ -45,9 +45,9 @@ and save them in a directory of your choice, for example, `/home/acmeuser/wls-in
 
  **NOTE**: You can provide the password in one of three ways:
 
- * Read from STDIN --password
- * Environment variable --passwordEnv
- * File containing the password --passwordFile
+ * Read from STDIN `--password`
+ * Environment variable `--passwordEnv`
+ * File containing the password `--passwordFile`
 
 
 You will see the Docker command output as the tool runs:

documentation/1.9/content/samples/patching-image.md

@@ -16,14 +16,14 @@ You can download patches using the Image Tool or by manually downloading them.
 
     For example, to download patch number `27342434` for WebLogic Server version 12.2.1.3.0:
 
-  ```bash
-  imagetool cache addPatch --patchId 27342434_12.2.1.3.0 --path /home/acmeuser/cache/p27342434_122130_Generic.zip
-  ```
+   ```bash
+   imagetool cache addPatch --patchId 27342434_12.2.1.3.0 --path /home/acmeuser/cache/p27342434_122130_Generic.zip
+   ```
 
-  **Note**: Refer to the [Cache](cache.md) commands for the format of ```patchId```.
+   **Note**: Refer to the [Cache]({{< relref "/userguide/tools/cache.md" >}}) commands for the format of ```patchId```.
 
 3. Use the [`imagetool update`]({{< relref "/userguide/tools/update-image.md" >}}) command to update the image:
 
-  ```bash
-  imagetool update --fromImage wls:12.2.1.3.0 --tag wls:12.2.1.3.4 --patches 27342434
-  ```
+   ```bash
+   imagetool update --fromImage wls:12.2.1.3.0 --tag wls:12.2.1.3.4 --patches 27342434
+   ```

documentation/1.9/content/userguide/prerequisites.md

@@ -5,7 +5,7 @@ draft: false
 weight: 1
 ---
 
-- Docker client and daemon on the build machine, with minimum Docker version 18.03.1.ce.
+- Docker client and daemon on the build machine, with a minimum Docker version 18.03.1.ce.
 - OPTIONALLY: Podman 3.x may be used in place of Docker.  
 - Installers for WebLogic Server and JDK from the [Oracle Software Delivery Cloud](https://edelivery.oracle.com).
 - When using any of the patching options, `--patches`, `--recommendedPatches`, or `--latestPSU`, you will need to provide [Oracle Support](https://www.oracle.com/technical-resources/) credentials.

documentation/1.9/content/userguide/setup.md

@@ -5,6 +5,6 @@ draft: false
 weight: 2
 ---
 
-- Download and unzip the release ZIP file to a desired location.
+- Download and unzip the WIT release ZIP file to a desired location.
 - OPTIONALLY: You may build the project (`mvn clean package`) to create the ZIP installer in `./imagetool/target`.
 - Set the JAVA_HOME environment variable to the location of the Java install (see [Prerequisites]({{< relref "/userguide/prerequisites.md" >}})).   

documentation/1.9/content/userguide/tools/_index.md

@@ -5,7 +5,5 @@ weight = 3
 pre = "<b> </b>"
 +++
 
-- [Create Image]({{< relref "/userguide/tools/create-image.md" >}}): The `create` command creates a new Docker image and installs the requested Java and WebLogic software.  In addition, you can create a WebLogic domain in the image at the same time.
-- [Rebase Image]({{< relref "/userguide/tools/rebase-image.md" >}}): The `rebase` command creates a new Docker image using an existing WebLogic domain from an existing image. The new Docker image can start from an existing image with a JDK and Oracle middleware installation, or can install the JDK and Oracle Home as part of moving the domain.
-- [Update Image]({{< relref "/userguide/tools/update-image.md" >}}): The `update` command creates a new Docker image by applying WebLogic patches to an existing image.  In addition, you can create a WebLogic domain if one did not exist previously, update an existing domain, or deploy an application.
-- [Cache]({{< relref "/userguide/tools/cache.md" >}}): The Image Tool maintains metadata on the local file system for patches and installers.  You can use the `cache` command to manipulate the local metadata.
+
+{{% children style="h4" description="true" %}}