edit release notes tense (#108)

Author: rosemarymarano

documentation/1.1/content/release/_index.md

@@ -12,41 +12,41 @@ pre = "<b> </b>"
 - [Known Issues](#known-issues)
 
 #### Major New Features
-No new features
+No new features.
 
 #### Other Changes
-- Revamp the Ingress Route editing mechanism:
-  - Add busy dialog while fetching existing service data from the domain's Kubernetes namespace prior to opening the route edit dialog.
-  - Add placeholders to the `Target Service` and `Target Port` fields to clarify the current state of these fields when no value is selected.
-  - Add logic to reset the `Target Port` field selection when the `Target Service` field changes and the selected port is not valid for the new service selected.
-- Rework the Image page and related fields on the Domain page to improve usability.  With these changes, a user not needing to create new images can bypass the Image page completely.
-  - Convert `Use Auxiliary Image` and `Create New Auxiliary Image` switches to radio buttons to make the three options a user has clearer.
-  - Move the `Image Tag` and `Image Registry Address` fields from the Image page tabs to the Domain page when not creating a new image.
-  - Replicate the `Create New Primary Image` and `Auxiliary Image Configuration` controls from the Image page to the Domain page.
-  - Add navigation buttons on the Domain page to direct the user to go back to the Image page when creating a new image.
-- Bundle WebLogic Deploy Tooling 2.1.0. See [WDT release notes](https://github.com/oracle/weblogic-deploy-tooling/releases/tag/release-2.1.0) for details.
-- Rework Model actions to work better for `Domain in Image` and `Domain in PV` use cases.
-  - Enhance Prepare Model action to use the new target types added in WebLogic Deploy Tooling 2.1.0 so that Prepare Model works properly for `Model in Image`, `Domain in Image` and `Domain in PV` use cases.
-  - Remove `Domain in PV` check that was previously preventing both `Validate Model` and `Prepare Model` actions from being used.
-- Enhance Domain page `Cluster` table to be editable when using `Domain in PV` to support use cases where the project has or doesn't have a model.
-- Convert all `aria-label` fields to use the i18n resource bundle.
-- Remove `webui` unit tests from the installers.
+- Revamped the Ingress Route editing mechanism:
+  - Added busy dialog while fetching existing service data from the domain's Kubernetes namespace prior to opening the route edit dialog.
+  - Added placeholders to the `Target Service` and `Target Port` fields to clarify the current state of these fields when no value is selected.
+  - Added logic to reset the `Target Port` field selection when the `Target Service` field changes and the selected port is not valid for the new service selected.
+- Reworked the Image page and related fields on the Domain page to improve usability.  With these changes, a user not needing to create new images can bypass the Image page completely.
+  - Converted `Use Auxiliary Image` and `Create New Auxiliary Image` switches to radio buttons to make the three options more clear.
+  - Moved the `Image Tag` and `Image Registry Address` fields from the Image page tabs to the Domain page when not creating a new image.
+  - Replicated the `Create New Primary Image` and `Auxiliary Image Configuration` controls from the Image page to the Domain page.
+  - Added navigation buttons on the Domain page to direct the user to go back to the Image page when creating a new image.
+- Bundled WebLogic Deploy Tooling 2.1.0. See [WDT release notes](https://github.com/oracle/weblogic-deploy-tooling/releases/tag/release-2.1.0) for details.
+- Reworked Model actions to work better for `Domain in Image` and `Domain in PV` use cases.
+  - Enhanced Prepare Model action to use the new target types added in WebLogic Deploy Tooling 2.1.0 so that Prepare Model works properly for `Model in Image`, `Domain in Image`, and `Domain in PV` use cases.
+  - Removed `Domain in PV` check that was previously preventing both `Validate Model` and `Prepare Model` actions from being used.
+- Enhanced Domain page `Cluster` table to be editable when using `Domain in PV` to support use cases where the project has or doesn't have a model.
+- Converted all `aria-label` fields to use the i18n resource bundle.
+- Removed `webui` unit tests from the installers.
 
 #### Bug Fixes
-- Resolve issue with "Save As" when saving project file in a different directory.
-- Resolve issue with "Save As" where the project was losing an entry for the archive file if no pending changes exist.
-- Resolve issue where project file to window mapping was causing unnecessary reassigning of the credential manager.
-- Add additional RPM installer dependencies to try to resolve installation issues when on a Linux VM not being used as a desktop machine.
-- Add a native macOS ICNS icon to resolve mangled icon on macOS.
-- Resolve issue with existing ingress route detection to eliminate overwrite warnings when route does not exist.
+- Resolved issue with "Save As" when saving project file in a different directory.
+- Resolved issue with "Save As" where the project was losing an entry for the archive file if no pending changes exist.
+- Resolved issue where project file to window mapping was causing unnecessary reassigning of the credential manager.
+- Added additional RPM installer dependencies to try to resolve installation issues when on a Linux VM not being used as a desktop machine.
+- Added a native macOS ICNS icon to resolve mangled icon on macOS.
+- Resolved issue with existing ingress route detection to eliminate overwrite warnings when route does not exist.
 
 ### Known Issues
 
-- When running the WKT UI application on Windows, the image builder tool (Docker or Podman) also must be directly 
+- When running the WKT UI application on Windows, the image builder tool (Docker or Podman) also must be directly
   executable in Windows.  For example, there is currently no support for running the WKT UI application in Windows and
   running Podman under the Windows Subsystem for Linux (WSL2).  However, running Docker Desktop for Windows with a WSL2
   backend _is_ fully supported because the `docker` command is executable directly in Windows (without having to call
-  WSL2). If you need to use Podman on Windows, then refer to the Podman blog entries at 
+  WSL2). If you need to use Podman on Windows, then refer to the Podman blog entries at
   https://podman.io/blogs/2021/09/06/podman-on-macs.html and https://podman.io/blogs/2020/09/02/running_windows_or_mac.html
   for more information about downloading, installing, and configuring the Windows Remote Client.