addressed PR feedback

Author: jjaygbay

articles/oracle/oracle-db/media/architecture-diagram.png

@@ -17,7 +17,7 @@ You access the OracleDB@Azure service through the Microsoft Azure portal. You cr
 There are IP address requirement differences between Oracle Database@Azure and Oracle Cloud Infrastructure (OCI).
 * Oracle Database@Azure reserves 13 IP addresses for the client subnet versus 3 for OCI requirements.
 
-For more information on specific Oracle Autonomous Database topics beyond their implementation and use within OracleDB@Azure, see [Using Oracle Autonomous Database Serverless](https://docs.oracle.com/en/cloud/paas/autonomous-database/serverless/adbsb/index.html).
+For more information on specific Oracle Autonomous Database articles beyond their implementation and use within OracleDB@Azure, see [Using Oracle Autonomous Database Serverless](https://docs.oracle.com/en/cloud/paas/autonomous-database/serverless/adbsb/index.html).
 
 The following articles provide specifics of the creation and management tasks associated with Autonomous Database services.
 

articles/oracle/oracle-db/oracle-database-autonomous-database-services.md

@@ -1,5 +1,5 @@
 ---
-title: Plan IP address space
+title: Plan IP address space for Oracle Database@Azure
 description: Learn about how to plan your IP address space for Oracle Database@Azure.
 author: jjaygbay1
 ms.service: oracle-on-azure
@@ -9,14 +9,16 @@ ms.date: 08/29/2024
 ms.author: jacobjaygbay
 ---
 
-# Plan for IP Address Space
+# Plan for IP Address Space for Oracle Database@Azure
+
+When you set up Oracle Database@Azure, you need to plan your IP address space to ensure that you have enough IP addresses for your virtual machine clusters and networking services.
 
 This article provides tables you can use to find the minimum subnet CIDR size for your Oracle Database@Azure Exadata service instance.
 
 Consider the following points when setting up networking:
 
 -   The minimum CIDR size is /27.
--   IP address ranges allocated to an Exadata VM cluster must not overlap with other CIDRs in use, as this overlap might cause routing issues. Take cross-region routing into consideration when configuring CIDRs for Oracle Database@Azure.
+-   IP address ranges allocated to an Exadata virtual machine cluster must not overlap with other CIDRs in use, as this overlap might cause routing issues. Take cross-region routing into consideration when configuring CIDRs for Oracle Database@Azure.
 -   For Exadata X9M: IP addresses XXX.XXX.X.X/XX and XXX.XXX.X.X/XX are reserved for the interconnect, and can't be allocated to client or backup networks.
 
 Other requirements specific to the Client Subnet and the Backup Subnet are provided in the sections for each subnet type that follow.
@@ -25,84 +27,82 @@ Other requirements specific to the Client Subnet and the Backup Subnet are provi
 
 The Client Subnet has the following IP address requirements:
 
--   Four IP addresses are needed for each virtual machine. VM clusters have a minimum of two virtual machines. Therefore, a VM cluster with two virtual machines requires eight IP addresses in the Client Subnet. Each additional virtual machine added to a VM cluster increases the number of IP addresses needed in the Client Subnet by 4 IPs.
--   Each VM cluster requires three IP addresses for Single Client Access Names \([SCANs](https://docs.oracle.com/en/cloud/paas/exadata-cloud/csexa/connect-db-using-net-services.html)\), regardless of how many virtual machines are present in the VM cluster.
--   17 IP addresses are reserved for networking services in the Client Subnet, regardless of how many VM clusters are present in the Client Subnet. The 17 addresses are the first 16 IP addresses, and the last IP address.
+-   Four IP addresses are needed for each virtual machine. virtual machine clusters have a minimum of two virtual machines. Therefore, a virtual machine cluster with two virtual machines requires eight IP addresses in the Client Subnet. Each additional virtual machine added to a virtual machine cluster increases the number of IP addresses needed in the Client Subnet by 4 IPs.
+-   Each virtual machine cluster requires three IP addresses for Single Client Access Names ([SCANs](https://docs.oracle.com/en/cloud/paas/exadata-cloud/csexa/connect-db-using-net-services.html)), regardless of how many virtual machines are present in the virtual machine cluster.
+-   17 IP addresses are reserved for networking services in the Client Subnet, regardless of how many virtual machine clusters are present in the Client Subnet. The 17 addresses are the first 16 IP addresses, and the last IP address.
 
-**Example**: IP addresses required for a Client Subnet that has one VM cluster with two virtual machines.
+**Example**: IP addresses required for a Client Subnet that has one virtual machine cluster with two virtual machines.
 
-``11 IPs *\(VM cluster with 2 virtual machines, plus 3 SCANs\)* + 17 IPs *\(Networking\)* = 28 IPs.``
+``11 IPs *(virtual machine cluster with 2 virtual machines, plus 3 SCANs)* + 17 IPs *(Networking)* = 28 IPs.``
 
-### VM cluster scenarios: CIDR size needed for the Client Subnet 
+### virtual machine cluster scenarios: CIDR size needed for the Client Subnet 
 
-The following table shows scenarios of provisioned VM clusters of differing sizes. The number of each scenario that can fit in a Client Subnet depends on the CIDR size used by the subnet. This table doesn't show all possible scenarios.
+The following table shows scenarios of provisioned virtual machine clusters of differing sizes. The number of each scenario that can fit in a Client Subnet depends on the CIDR size used by the subnet. This table doesn't show all possible scenarios.
 
 |Scenario|/27|/26|/25|/24|/23|/22|
 |--------|---|---|---|---|---|---|
-|1 VM cluster with 2 virtual machines *\(11 IPs + 17 Networking = 28\)*|1|4|10|21|45|91|
-|1 VM cluster with 3 virtual machines *\(15 IPs + 17 Networking = 32*|1|3|7|15|33|67|
-|1 VM cluster with 4 virtual machines *\(19 IPs + 17 Networking = 36\)*| |2|5|12|26|53|
-|2 VM clusters with 2 virtual machines each *\(22 IPs + 17 Networking = 39\)*| |2|5|10|22|45|
-|2 VM clusters with 3 virtual machines each *\(30 IPs + 17 Networking = 47\)*| |1|3|7|16|33|
-|2 VM clusters with 4 virtual machines each *\(38 IPs + 17 Networking = 55\)*| |1|2|6|13|26|
+|1 virtual machine cluster with 2 virtual machines *(11 IPs + 17 Networking = 28)*|1|4|10|21|45|91|
+|1 virtual machine cluster with 3 virtual machines *(15 IPs + 17 Networking = 32*|1|3|7|15|33|67|
+|1 virtual machine cluster with 4 virtual machines *(19 IPs + 17 Networking = 36)*| |2|5|12|26|53|
+|2 virtual machine clusters with 2 virtual machines each *(22 IPs + 17 Networking = 39)*| |2|5|10|22|45|
+|2 virtual machine clusters with 3 virtual machines each *(30 IPs + 17 Networking = 47)*| |1|3|7|16|33|
+|2 virtual machine clusters with 4 virtual machines each *(38 IPs + 17 Networking = 55)*| |1|2|6|13|26|
 
-### VM cluster scenarios: CIDR size needed for the Client Subnet 
+### virtual machine cluster scenarios: CIDR size needed for the Client Subnet 
 
-The following table shows scenarios of provisioned VM clusters of differing sizes. The number of each scenario that can fit in a Client Subnet depends on the CIDR size used by the subnet. This table doesn't show all possible scenarios.
+The following table shows scenarios of provisioned virtual machine clusters of differing sizes. The number of each scenario that can fit in a Client Subnet depends on the CIDR size used by the subnet. This table doesn't show all possible scenarios.
 
 |Scenario|/27|/26|/25|/24|/23|/22|
 |--------|---|---|---|---|---|---|
-|1 VM cluster with 2 virtual machines *\(11 IPs + 17 Networking = 28\)*|1|2|4|9|18|36|
-|1 VM cluster with 3 virtual machines *\(15 IPs + 17 Networking = 32*|1|2|4|8|16|32|
-|1 VM cluster with 4 virtual machines *\(19 IPs + 17 Networking = 36\)*| |1|3|7|14|28|
-|2 VM clusters with 2 virtual machines each *\(22 IPs + 17 Networking = 39\)*| |1|3|6|13|26|
-|2 VM clusters with 3 virtual machines each *\(30 IPs + 17 Networking = 47\)*| |1|2|5|10|21|
-|2 VM clusters with 4 virtual machines each *\(38 IPs + 17 Networking = 55\)*| |1|2|4|9|18|
+|1 virtual machine cluster with 2 virtual machines *(11 IPs + 17 Networking = 28)*|1|2|4|9|18|36|
+|1 virtual machine cluster with 3 virtual machines *(15 IPs + 17 Networking = 32)*|1|2|4|8|16|32|
+|1 virtual machine cluster with 4 virtual machines *(19 IPs + 17 Networking = 36)*| |1|3|7|14|28|
+|2 virtual machine clusters with 2 virtual machines each *(22 IPs + 17 Networking = 39)*| |1|3|6|13|26|
+|2 virtual machine clusters with 3 virtual machines each *(30 IPs + 17 Networking = 47)*| |1|2|5|10|21|
+|2 virtual machine clusters with 4 virtual machines each *(38 IPs + 17 Networking = 55)*| |1|2|4|9|18|
 
 ## Backup Subnet requirements 
 
 The Backup Subnet has the following IP address requirements:
 
--   3 IP addresses for each virtual machine. VM clusters have a minimum of 2 virtual machines. Therefore, a VM cluster with 2 virtual machines requires 6 IP addresses in the backup subnet. Each additional virtual machine added to a VM cluster increases the number of IP addresses needed in the Backup Subnet by 3 IPs.
--   Networking services require 3 IP addresses for the Backup Subnet, regardless of how many VM clusters are present in the Backup Subnet.
+-   3 IP addresses for each virtual machine. virtual machine clusters have a minimum of 2 virtual machines. Therefore, a virtual machine cluster with 2 virtual machines requires 6 IP addresses in the backup subnet. Each additional virtual machine added to a virtual machine cluster increases the number of IP addresses needed in the Backup Subnet by 3 IPs.
+-   Networking services require 3 IP addresses for the Backup Subnet, regardless of how many virtual machine clusters are present in the Backup Subnet.
 
-**Example**: IP addresses required for a Backup Subnet that has 1 VM cluster with 2 virtual machines. 
+**Example**: IP addresses required for a Backup Subnet that has 1 virtual machine cluster with 2 virtual machines. 
 
-``6 IPs *\(VM cluster with 2 virtual machines\)* + 3 IPs *\(Networking\)* = 9 IPs.``
+``6 IPs *(virtual machine cluster with 2 virtual machines)* + 3 IPs *(Networking)* = 9 IPs.``
 
-### VM cluster scenarios: CIDR size needed for the Backup Subnet
+### virtual machine cluster scenarios: CIDR size needed for the Backup Subnet
 
-The following table shows scenarios of provisioned VM clusters of differing sizes. The number of each scenario that can fit in a Backup Subnet depends on the CIDR size used by the subnet. This table doesn't display all possible scenarios.
+The following table shows scenarios of provisioned virtual machine clusters of differing sizes. The number of each scenario that can fit in a Backup Subnet depends on the CIDR size used by the subnet. This table doesn't display all possible scenarios.
 
 |Scenario|/28|/27|/26|/25|/24|/23|
 |--------|---|---|---|---|---|---|
-|1 VM cluster with 2 virtual machines *\(6 IPs + 3 Networking = 9\)*|1|3|7|14|28|56|
-|1 VM cluster with 3 virtual machines *\(9 IPs + 3 Networking = 12\)*|1|2|5|10|21|42|
-|1 VM cluster with 4 virtual machines *\(12 IPs + 3 Networking = 15\)*|1|2|4|8|17|34|
-|2 VM clusters with 2 virtual machines each *\(12 IPs + 3 Networking = 15\)*|1|2|4|8|17|34|
-|2 VM clusters with 3 virtual machines each *\(18 IPs + 3 Networking = 21\)*| |1|3|6|12|24|
-|2 VM clusters with 4 virtual machines each *\(24 IPs + 3 Networking = 27\)*| |1|2|4|9|18|
+|1 virtual machine cluster with 2 virtual machines *(6 IPs + 3 Networking = 9)*|1|3|7|14|28|56|
+|1 virtual machine cluster with 3 virtual machines *(9 IPs + 3 Networking = 12)*|1|2|5|10|21|42|
+|1 virtual machine cluster with 4 virtual machines *(12 IPs + 3 Networking = 15)*|1|2|4|8|17|34|
+|2 virtual machine clusters with 2 virtual machines each *(12 IPs + 3 Networking = 15)*|1|2|4|8|17|34|
+|2 virtual machine clusters with 3 virtual machines each *(18 IPs + 3 Networking = 21)*| |1|3|6|12|24|
+|2 virtual machine clusters with 4 virtual machines each *(24 IPs + 3 Networking = 27)*| |1|2|4|9|18|
 
 ## Usable IPs for client and Backup subnets by CIDR size 
 
-The following table shows the number of IPs available for VM clusters and SCANs for various CIDR sizes, after subtracting the IPs required by the Networking services.
+The following table shows the number of IPs available for virtual machine clusters and SCANs for various CIDR sizes, after subtracting the IPs required by the Networking services.
 
 >[!Tip] 
-> Allocating a larger space for the subnet than the minimum required \(for example, at least /25 instead of /27\) can reduce the relative impact of those reserved addresses on the subnet's available space.
+> Allocating a larger space for the subnet than the minimum required (for example, at least /25 instead of /27) can reduce the relative impact of those reserved addresses on the subnet's available space.
 
-|Subnet CIDR|Reserved Networking IPs for Client Subnet|Usable IPs for Client Subnet \(Virtual Machines and SCANs\)|Reserved Networking IPs for Backup Subnet|Usable IPs for Backup Subnet \(Virtual Machines and SCANs\)|
+|Subnet CIDR|Reserved Networking IPs for Client Subnet|Usable IPs for Client Subnet (Virtual Machines and SCANs)|Reserved Networking IPs for Backup Subnet|Usable IPs for Backup Subnet (Virtual Machines and SCANs)|
 |-----------|-----------------------------------------|-----------------------------------------------------------|-----------------------------------------|-----------------------------------------------------------|
-|/28|17|0 \(2^4 - 17\)|3|13 \(2^4 - 3\)|
-|/27|17|15 \(2^5 - 17\)|3|29 \(2^5 - 3\)|
-|/26|17|47 \(2^6 - 17\)|3|61 \(2^6 - 3\)|
-|/25|17|111 \(2^7 - 17\)|3|125 \(2^7 - 3\)|
-|/24|17|239 \(2^8 - 17\)|3|253 \(2^8 - 3\)|
-|/23|17|495 \(2^9 - 17\)|3|509 \(2^9 - 3\)|
-|/22|17|1007 \(2^10 - 17\)|3|1021 \(2^10 - 3\)|
+|/28|17|0 (2^4 - 17)|3|13 (2^4 - 3)|
+|/27|17|15 (2^5 - 17)|3|29 (2^5 - 3)|
+|/26|17|47 (2^6 - 17)|3|61 (2^6 - 3)|
+|/25|17|111 (2^7 - 17)|3|125 (2^7 - 3)|
+|/24|17|239 (2^8 - 17)|3|253 (2^8 - 3)|
+|/23|17|495 (2^9 - 17)|3|509 (2^9 - 3)|
+|/22|17|1007 (2^10 - 17)|3|1021 (2^10 - 3)|
 
 ## Next steps
- 
-- [Onboard with Oracle Database@Azure](onboard-oracle-database.md)
 - [Provision and manage Oracle Database@Azure](provision-oracle-database.md)
 - [Oracle Database@Azure support information](oracle-database-support.md)
 - [Network planning for Oracle Database@Azure](oracle-database-network-plan.md)

articles/oracle/oracle-db/oracle-database-plan-ip.md

@@ -1,6 +1,6 @@
 ---
-title: Database operations processes for Exadata services
-description: Learn about database operations processes for Exadata services.
+title: Database operations processes for autonomous recovery Service@Azure
+description: Learn about database operations processes for autonomous recovery Service@Azure.
 author: jjaygbay1
 ms.author: jacobjaygbay
 ms.topic: concept-article
@@ -12,7 +12,7 @@ ms.date: 08/01/2024
 
 There are Oracle processes that are accessible from Microsoft Azure, but are setup and maintained from the Oracle Cloud Infrastructure (OCI) console.
 
-## Oracle Database Autonomous Recovery Service@Azure
+## Oracle database Autonomous Recovery Service@Azure
 
 Oracle Database Autonomous Recovery Service@Azure (RCV) is the preferred backup solution for OracleDB@Azure resources. The key customer benefits are as follows:
 * Allows use of Microsoft Azure Consumption Commitment (MACC) to pay for your backup storage.

articles/oracle/oracle-db/oracle-database-processes-autonomous-database-services.md

@@ -1,18 +1,18 @@
 ---
-title: Provision an autonomous database
-description: Learn about how to provision an autonomous database.
+title: Provision an autonomous database serverless instance
+description: Learn about how to provision an autonomous database serverless instance.
 author: jjaygbay1
 ms.author: jacobjaygbay
 ms.topic: concept-article
 ms.service: oracle-on-azure
 ms.date: 08/01/2024
 ---
-# Provision an autonomous database
+# Provision an autonomous database serverless instance
 
 Provisioning and basic management functions for an Oracle Autonomous Database Serverless instance is done from the Oracle Autonomous Database@Azure blade. More management functions are available within the Oracle Cloud Infrastructure (OCI) portal available via the link to that Oracle Autonomous Database from the Oracle Autonomous Database@Azure blade.
 
->[!NOTE] 
-> There are prerequisites that must be completed before you can provision Exadata Services. You need to complete the following:
+## Prerequisites
+The following are prerequisites that must be completed before you can provision Exadata Services. 
 
 - An existing Azure subscription
 - An Azure virtual network with a subnet delegated to the Oracle Database@Azure service (`Oracle.Database/networkAttachments`)

articles/oracle/oracle-db/oracle-database-provision-autonomous-database.md

@@ -6,7 +6,7 @@ ms.service: oracle-on-azure
 ms.collection: linux
 ms.topic: article
 ms.date: 9/24/2024
-ms.custom: engagement-fy23
+ms.custom: references-regions
 ms.author: jacobjaygbay
 ---