proofread

jjaygbay · jjaygbay · commit 3350c94d7a95 · 2024-06-10T16:47:35.000-04:00
diff --git a/articles/oracle/oracle-db/provision-oracle-exadata-infrastructure.md b/articles/oracle/oracle-db/provision-oracle-exadata-infrastructure.md
@@ -17,16 +17,17 @@ Provisioning Oracle Exadata Infrastructure is a time-consuming process. Provisio
 > [!NOTE]
 > To ensure you have all the information needed for a successful provisioning flow, review the [Provisioning Troubleshooting](https://docs.oracle.com/en-us/iaas/odaaz/odaaz-provisioningtroubleshooting.html#GUID-DACCA740-025E-4466-8BB7-AC8C1D23E450) document specifically the IP Address Requirement Differences.
 
-1. Provision your Oracle Exadata Infrastructure and Oracle Exadata VM Cluster resources from the OracleDB@Azure blade. By default, the Oracle Exadata Infrastructure tab is selected. To create a Oracle Exadata VM Cluster resource, select that tab first.
+1. Provision your Oracle Exadata Infrastructure and Oracle Exadata VM Cluster resources from the OracleDB@Azure blade. By default, the Oracle Exadata Infrastructure tab is selected. To create an Oracle Exadata VM Cluster resource, select that tab first.
 1. Select the **+ Create** icon at the top of the blade to begin the provisioning flow.
-1. Check that you are the **Create** Oracle Exadata Infrastructure flow. If not, exit the flow.
+1. Check that you're the **Create** Oracle Exadata Infrastructure flow. If not, exit the flow.
 1. From the **Basics** tab of the Create Oracle Exadata Infrastructure flow, enter the following information.
    1. Select the Microsoft Azure subscription to which the Oracle Exadata Infrastructure will be provisioned and billed.
-   1. Select an existing **Resource group** or select the **Create new** link to create and use a new Resource group for this resource. A resouce group is a collection of resources sharing the same lifecycle, permissions, and policies.
+   1. Select an existing **Resource group** or select the **Create new** link to create and use a new Resource group for this resource. A resource group is a collection of resources sharing the same lifecycle, permissions, and policies.
    1. Enter a unique **Name** for the Oracle Exadata Infrastructure on this subscription.
-   1. Select the **Region** where this Oracle Exadata Infrastructure will be provisioned. **NOTE:** The regions where the OracleDB@Azure service is available are limited.
-   1. Select the **Availability zone** where this Oracle Exadata Infrastructure will be provisioned. **NOTE:** The availability zones where the OracleDB@Azure service is available are limited.
-   1. The **Oracle Cloud account name** field is display-only. If the name is not showing correctly, your OracleDB@Azure account setup has not been successfully completed.
+   1. Select the **Region** where this Oracle Exadata Infrastructure is provisioned. **NOTE:** The regions where the OracleDB@Azure service is available are limited.
+   1. Select the **Availability zone** where this Oracle Exadata Infrastructure is provisioned.
+     > [!NOTE] The availability zones where the OracleDB@Azure service is available are limited.
+   1. The **Oracle Cloud account name** field is display-only. If the name isn't showing correctly, your OracleDB@Azure account setup hasn't been successfully completed.
    1. Select **Next** to continue.
 1. From the **Configuration** tab of the Create Oracle Exadata Infrastructure flow, enter the following information.
    1. From the dropdown list, select the **Exadata infrastructure model** you want to use for this deployment. **NOTE:** Not all Oracle Exadata Infrastructure models are available. For more information, see [Oracle Exadata Infrastructure Models](https://docs.oracle.com/iaas/exadatacloud/exacs/ecs-ovr-x8m-scable-infra.html#GUID-15EB1E00-3898-4718-AD94-81BDE271C843).
@@ -35,13 +36,13 @@ Provisioning Oracle Exadata Infrastructure is a time-consuming process. Provisio
    1. The **OCPUs** and **Storage** fields are automatically updated based on the settings of the Database servers and Storage servers selectors.
    1. Select **Next** to continue.
 1. From the **Maintenance** tab of the Create Oracle Exadata Infrastructure flow, enter the following information.
-   1. The **Maintenance method** is selectable to either Rolling or Non-rolling based on your patching preferences.
+   1. The **Maintenance method** is selectable to either Rolling or Nonrolling based on your patching preferences.
    1. By default, the **Maintenance schedule** is set to **No preference**.
-   1. If you select **Specify a schedule for the Maintenance schedule**, additional options open for you to tailor a maintenance schedule that meets your requirements. Each of these selections requires at least one option in each field.
+   1. If you select **Specify a schedule for the Maintenance schedule**, other options open for you to tailor a maintenance schedule that meets your requirements. Each of these selections requires at least one option in each field.
    1. You can then enter up to 10 **Names** and **Email addresses** that are used as contacts for the maintenance process.
    1. Select **Next** to continue.
 1. From the **Consent** tab of the Create Oracle Exadata Infrastructure flow, you must agree to the terms of service, privacy policy, and agree to access permissions. Once accepted, select **Next** to continue.
-1. From the **Tags** tab of the Create Oracle Exadata Infrastructure flow, you define Microsoft Azure tags. **NOTE:** These tags are not propagated to the Oracle Cloud Infrastructure (OCI) portal. Once you have created the tags, if any, for your environment, select **Next** to continue.
+1. From the **Tags** tab of the Create Oracle Exadata Infrastructure flow, you define Microsoft Azure tags. **NOTE:** These tags aren't propagated to the Oracle Cloud Infrastructure (OCI) portal. Once you have created the tags, if any, for your environment, select **Next** to continue.
 1. From the **Review _+** create tab of the Create Oracle Exadata Infrastructure flow, a short validation process is run to check the values that you entered from the previous steps. If the validation fails, you must correct any errors before you can start the provisioning process.
 1. Select the **Create** button to start the provisioning flow.
 1. Return to the Oracle Exadata Infrastructure blade to monitor and manage the state of your Oracle Exadata Infrastructure environments.
diff --git a/articles/oracle/oracle-db/provision-oracle-exadata-vm-cluster.md b/articles/oracle/oracle-db/provision-oracle-exadata-vm-cluster.md
@@ -18,19 +18,19 @@ Provisioning an Oracle Exadata VM Cluster requires the existence of an Oracle Ex
 > [!NOTE]
 > Review the [Provisioning Troubleshooting](https://docs.oracle.com/en-us/iaas/odaaz/odaaz-provisioningtroubleshooting.html#GUID-DACCA740-025E-4466-8BB7-AC8C1D23E450), specifically the IP Address Requirement Differences, to ensure you have all the information needed for a successful provisioning flow.
 
-1. You provision Oracle Exadata Infrastructure and Oracle Exadata VM Cluster resources from the OracleDB@Azure blade. By default, the Oracle Exadata Infrastructure tab is selected. To create a Oracle Exadata VM Cluster resource, select that tab first.
+1. You provision Oracle Exadata Infrastructure and Oracle Exadata VM Cluster resources from the OracleDB@Azure blade. By default, the Oracle Exadata Infrastructure tab is selected. To create an Oracle Exadata VM Cluster resource, select that tab first.
 1. Select the **+ Create** icon at the top of the blade to begin the provisioning flow.
-1. Check that you are using the **Create** Oracle Exadata VM Cluster flow. If not, exit the flow.
-1. From the **Basics** tab of the Create Oracle Exadata VM Cluster flow, enter the following information. **NOTE:** Before you can provision an Oracle Exadata VM Cluster, you must have a provisioned Oracle Exadata Infrastructure which you will assign for your Oracle Exadata VM Cluster.
+1. Check that you're using the **Create** Oracle Exadata VM Cluster flow. If not, exit the flow.
+1. From the **Basics** tab of the Create Oracle Exadata VM Cluster flow, enter the following information. **NOTE:** Before you can provision an Oracle Exadata VM Cluster, you must have a provisioned Oracle Exadata Infrastructure, which you'll assign for your Oracle Exadata VM Cluster.
    1. Select the Microsoft Azure subscription to which the Oracle Exadata VM Cluster will be provisioned.
    1. Select an existing **Resource group** or select the **Create new** link to create and use a new Resource group for this resource.
    1. Enter a unique **Name** for the Oracle Exadata VM Cluster on this subscription.
-   1. Select the **Region** where this Oracle Exadata Infrastructure will be provisioned. **NOTE:** The regions where the OracleDB@Azure service is available are limited, and you should assign the Oracle Exadata VM Cluster to the same region as the parent Oracle Exadata Infrastructure.
-   1. The **Cluster name** should match the Name to avoid additional naming conflicts.
-   1. Select the existing **Exadata infrastructure** that will be the parent for your Oracle Exadata VM Cluster.
-   1. The **License type** is either **License included** or **Bring your own license (BYOL)**. Your selection will affect your billing.
-   1. The default **Time zone** is UTC. There is also an option to **Select another time zone**.
-   1. If you choose the **Select another time zone** option, two additional required fields will open, **Region or country** and **Selected time zone**. Both of these fields are drop-down lists with selectable values. Once you select the **Region or country**, the **Selected time zone** will be populated with the available values for that **Region or country**.
+   1. Select the **Region** where this Oracle Exadata Infrastructure is provisioned. **NOTE:** The regions where the OracleDB@Azure service is available are limited, and you should assign the Oracle Exadata VM Cluster to the same region as the parent Oracle Exadata Infrastructure.
+   1. The **Cluster name** should match the Name to avoid other naming conflicts.
+   1. Select the existing **Exadata infrastructure** that is the parent for your Oracle Exadata VM Cluster.
+   1. The **License type** is either **License included** or **Bring your own license (BYOL)**. Your selection affects your billing.
+   1. The default **Time zone** is UTC. There's also an option to **Select another time zone**.
+   1. If you choose the **Select another time zone** option, two more required fields open, **Region or country** and **Selected time zone**. Both of these fields are drop-down lists with selectable values. Once you select the **Region or country**, the **Selected time zone** is populated with the available values for that **Region or country**.
    1. The **Grid Infrastructure Version** is selectable based on your previous selections. The **Grid Infrastructure Version** limits the Oracle Database versions that the Oracle Exadata VM Cluster supports.
    1. If selected, the **Choose Exadata Image version** checkbox allows you to select whether or not to **Include Exadata Image minor versions** as selectable, and then to choose the specific **Exadata Image version** from the drop-down field based on whether or not you allowed **Include Exadata Image minor versions**.
    1. The **SSH public key source** can be selected to **Generate new key pair**, **Use existing key stored in Azure**, or **Use existing public key**. If you select **Generate new key pair**, you must give your newly generated key a unique name. If you select **Use existing key stored in Azure**, you must select that key from a dropdown of defined key for your subscription. If you select **Use existing public key**, you must provide an RSA public key in sing-line format (starting with "ssh-rsa") or the multi-line PEM format. You can generate SSH keys using ssh-keygen or Linux and OS X, or PuTTYGen on Windows.
@@ -50,11 +50,11 @@ Provisioning an Oracle Exadata VM Cluster requires the existence of an Oracle Ex
    1. If checked, a list of existing DNS private views from OCI is presented. Select the view to use. To create a new private view and zones, see [Private DNS](https://docs.oracle.com/iaas/Content/DNS/Tasks/privatedns.htm).
    1. Enter the **Host name** prefix. The prefix forms forms the first portion of the Oracle Exadata VM Cluster host name.
    1. The **Host domain name** and **Host and domain URL** for your Oracle Exadata VM Cluster are read-only and populated with derived naming.
-   1. Within the **Network ingress rules** section, the **Add additional network ingress rules** checkbox allows you to define addition ingress CIDR rules. Additional network CIDR ranges (such as application or hub subnet ranges) can be added, during provisioning, to the network security group (NSG) ingress rules for the VM cluster. The selected virtual network's CIDR is added by default. CIDR ranges are specified. The port can be a single port, port range (for example, 80-8080), a comma-delimited list of ports (for example, 80,8080), or any combination of these. This only updates the OCI network security group ingress rules. Microsoft Azure VNet network security rules must be updated in the specific VNet in Microsoft Azure.
+   1. Within the **Network ingress rules** section, the **Add additional network ingress rules** checkbox allows you to define addition ingress CIDR rules. Other network CIDR ranges (such as application or hub subnet ranges) can be added, during provisioning, to the network security group (NSG) ingress rules for the VM cluster. The selected virtual network's CIDR is added by default. CIDR ranges are specified. The port can be a single port, port range (for example, 80-8080), a comma-delimited list of ports (for example, 80,8080), or any combination of these port ranges. This only updates the OCI network security group ingress rules. Microsoft Azure virtual network network security rules must be updated in the specific virtual network in Microsoft Azure.
    1. Select **Next** to continue.
-1. From the **Diagnostics Collection** tab of the Create Oracle Exadata VM Cluster flow allow you to specify the diagnostic events, health monitoring, and incident logs and tracing that Oracle can use to identify, track, and resolve issues. Select **Next** to continue.
-1. From the **Consent** tab of the Create Oracle Exadata VM Cluster flow, you must agree to the terms of service, privacy policy, and agree to access permissions. Select **Next** to continue.
-1. From the **Tags** tab of the Create Oracle Exadata VM Cluster flow, you can define Microsoft Azure tags. **NOTE:** These tags are not propagated to the Oracle Cloud Infrastructure (OCI) portal. Select **Next** to continue.
+1. From the **Diagnostics Collection** tab of the Create Oracle Exadata VM Cluster flow allows you to specify the diagnostic events, health monitoring, and incident logs and tracing that Oracle can use to identify, track, and resolve issues. Select **Next** to continue.
+1. From the **Consent** tab of the **Create Oracle Exadata VM Cluster** flow, you must agree to the terms of service, privacy policy, and agree to access permissions. Select **Next** to continue.
+1. From the **Tags** tab of the Create Oracle Exadata VM Cluster flow, you can define Microsoft Azure tags. **NOTE:** These tags aren't propagated to the Oracle Cloud Infrastructure (OCI) portal. Select **Next** to continue.
 1. From the **Review _+ create** tab of the Create Oracle Exadata VM Cluster flow, a short validation process is run to check the values that you entered from the previous steps. If the validation fails, you must correct any errors before you can start the provisioning process.
 1. Select the **Create** button to start the provisioning flow.
 1. Return to the Oracle Exadata VM Cluster blade to monitor and manage the state of your Oracle Exadata VM Cluster environments.
