diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/README.md
index ab7da2943..3092ce026 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/README.md
@@ -2,7 +2,7 @@
  
 Oracle Cloud VMware Solution is based on VMware Cloud Foundation (VCF) and provides a fully supported, customizable cloud environment for VMware deployments and migrations. The solution delivers a full-stack software-defined data center (SDDC), including VMware’s vCenter, ESXi, NSX, and vSAN. Specific use cases targeted by Oracle Cloud VMware Solution include data center and application migration, hybrid extension, on-demand capacity, and disaster recovery. 
 
-Reviewed: 26.11.2025
+Reviewed: 24.06.2026
  
 # Table of Contents
  
@@ -20,6 +20,14 @@ Reviewed: 26.11.2025
 
 ## Reference Architectures & Step-by-step Guides
 
+### Deployment Guides
+
+- [Architecting Multi-Region Networking and Security with NSX Federation in OCVS - Part 1](https://blogs.oracle.com/cloud-infrastructure/nsx-fed-ocvs)
+    - This deployment guide shows the deployment and use cases for NSX Federation with Oracle Cloud VMware Solution and VCF BYOL licensing.
+
+- [Architecting Multi-Region Networking and Security with NSX Federation in OCVS - Part 2: Edge Clusters, Federated Routing, and North-South Connectivity](https://blogs.oracle.com/cloud-infrastructure/nsx-fed-ocvs-part2-edge-routing-and-ns-connectivity)
+    - This deployment guide covers dedicated federation edge clusters, RTEPs, Federated Tier-0 and Tier-1 gateways, stretched segments, and north-south connectivity for cross-site workloads.
+
 - [Deploy a VMware vSAN stretched cluster across OCI regions with Oracle Cloud VMware Solution](https://docs.oracle.com/en/solutions/ocvs-vsan-stretched-cluster/index.html) 
     - This solution playbook describes deploying Oracle Cloud VMware Solution with a VMware vSAN stretched cluster across multiple OCI regions (with a vSAN Witness in a third region) to achieve region-level availability and resilience.
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/disaster-recovery-to-ocvs-solution-definition/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/disaster-recovery-to-ocvs-solution-definition/README.md
index 08e342206..d0167a4a6 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/disaster-recovery-to-ocvs-solution-definition/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/disaster-recovery-to-ocvs-solution-definition/README.md
@@ -2,7 +2,7 @@
 
 This repository contains a detailed guide for the disaster recovery of VMware workloads to Oracle Cloud VMware Solution. It offers a high-level solution definition of the deployment architecture and tools like Site Recovery Manager or HCX. The document is aimed at capturing the current state architecture and provides a prospective state, potential project scope, RPO/RTO requirements and target OCVS architecture.
 
-Reviewed: 12.11.2025
+Reviewed: 24.06.2026
 
 # When to use this asset?
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/disaster-recovery-to-ocvs-solution-definition/files/OCVS-Disaster-Recovery-Solution-Definition-Template.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/disaster-recovery-to-ocvs-solution-definition/files/OCVS-Disaster-Recovery-Solution-Definition-Template.md
index 7228fd680..e6d0b0c76 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/disaster-recovery-to-ocvs-solution-definition/files/OCVS-Disaster-Recovery-Solution-Definition-Template.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/disaster-recovery-to-ocvs-solution-definition/files/OCVS-Disaster-Recovery-Solution-Definition-Template.md
@@ -22,22 +22,22 @@ doc:
       authors: 
         - Base Template
       comments:
-        - Created a new Solution Definition document. To be used for iterative review and improvement.
+        - Created a new Solution Definition document for iterative review and improvement.
     - version: 1.1
       date: 1st July 2023
       authors: Base Template
       comments:
-        - Update Template per feedback. Added security-templated texts and annex.
+        - Updated the template based on feedback. Added security template text and annex content.
     - version: 1.2
       date: 1st August 2023
       authors: Base Template
       comments:
-        - Update Template per feedback. As per Confluence.
+        - Updated the template based on Confluence feedback.
     - version: 2
       date: 1st September 2023
       authors: Base Template
       comments:
-        - Added Networking Annex
+        - Added Networking Annex.
     - version: 2.1
       date: 1st September 2023
       authors: Base Template
@@ -54,17 +54,17 @@ doc:
       authors: Base Template
       comments:
         - Added comment for workload snippets
-        - Updates Acronyms
+        - Updated acronyms.
     - version: 2.4
       date: 26th February 2024
       authors: Base Template
       comments:
-        - Added the network firewall in the requirement, the solution considerations, and in the Annex.
+        - Added network firewall guidance to the requirements, solution considerations, and annex.
     - version: 2.5
       date: 8th April 2024
       authors: Base Template
       comments:
-        - Added 'manageability' in the requirement, the solution considerations, and in the Annex.
+        - Added manageability guidance to the requirements, solution considerations, and annex.
   team:
     - name: ${doc.author}
       email: example@example.com
@@ -111,7 +111,7 @@ PPM   | None
 
 *Guide:*
 
-*The first chapter of the document describes the metadata for the document. Such as versioning and team members.*
+*The first chapter describes document metadata, including version history and team members.*
 
 ## Version Control
 <!--
@@ -124,12 +124,12 @@ PPM   | None
 
 *Guide:*
 
-*A section describing the versions of this document and its changes.*
+*Use this section to describe document versions and the changes introduced in each version.*
 
 *Example:*
 
 ```{#history}
-This is the document history. Please use doc.history metadata for compiling the table
+This is the document history. Use the doc.history metadata to compile the table.
 ```
 
 ## Team
@@ -143,12 +143,12 @@ PPM   | None
 
 *Guide:*
 
-*A section describing the team.*
+*Use this section to describe the delivery team.*
 
 *Example:*
 
 ```{#team}
-This is the team that is delivering the WAD. Please use doc.team metadata for compiling the table
+This is the team delivering the workload architecture document. Use the doc.team metadata to compile the table.
 ```
 
 ## Document Purpose
@@ -162,7 +162,7 @@ PPM   | None
 
 *Guide:*
 
-*Describe the purpose of this document and the Oracle-specific terminology, specifically around 'Workload'.*
+*Describe the purpose of this document and define any Oracle-specific terminology, especially the term 'Workload'.*
 
 <!--                            -->
 <!-- End of 1) Document Control -->
@@ -179,7 +179,7 @@ PPM   | None
 
 *Guide:*
 
-*Describe the customer's business and background. What is the context of the customer's industry and LoB? What are the business needs and goals that this Workload is an enabler for? How does this technical solution impact and support the customer's business goals? Does this solution support a specific customer strategy, or maybe certain customer values? How does this solution help our customers to either generate more revenue or save costs?*
+*Describe the customer's business context and background. Include the customer's industry, line of business, business needs, and goals enabled by this workload. Explain how the technical solution supports those goals, whether it aligns with a specific customer strategy or customer values, and how it helps the customer generate revenue, reduce cost, or reduce risk.*
 
 
 ## Executive Summary
@@ -193,7 +193,7 @@ PPM   | None
 
 *Guide:*
 
-*A section describing the Oracle differentiator and key values of the solution of our solution for the customer, allowing the customer to make decisions quickly.*
+*Describe the Oracle differentiators and key customer value of the proposed solution so decision makers can understand the recommendation quickly.*
 
 ## Workload Business Value
 <!--
@@ -210,7 +210,7 @@ PPM   | None
 <!-- End of 2) Business Context -->
 <!--                            -->
 
-The Oracle Cloud VMware Solution is a customer-managed Software-defined Data Center solution offering customers a choice to run flexible infrastructure to host mission-critical workloads. The customer can seamlessly migrate or protect workloads from the on-premises VMware environment to Oracle Cloud VMware Solution promptly with the help of the native migration and disaster recovery tool offered with the solution. Since the platform remains the same there are no efforts required to re-factor the applications rather customer can focus on the cloud transformation journey.
+Oracle Cloud VMware Solution is a customer-managed software-defined data center (SDDC) service that provides flexible infrastructure for mission-critical VMware workloads. Customers can migrate or protect workloads from an on-premises VMware environment to Oracle Cloud VMware Solution by using native migration and disaster recovery tooling available with the service. Because the VMware platform remains consistent, customers can reduce or avoid application refactoring and focus on their broader cloud transformation journey.
 
 # Workload Requirements and Architecture
 
@@ -225,28 +225,28 @@ PPM   | None
 
 *Guide:*
 
-*Describe the Workload: What applications and environments are part of this Workload migration or new implementation project, and what are their names? The implementation will be scoped later and can be a subset of the Solution Definition and proposed overall solution. For example, a Workload could exist of two applications, but the implementer would only include one environment of one application. The workload chapter is about the whole Workload and the implementation scope will be described later in the chapter [Solution Scope](#solution-scope).*
+*Describe the workload. Identify the applications and environments included in this migration, disaster recovery, or new implementation project. The implementation scope is defined later and can be a subset of the overall Solution Definition. For example, a workload might include two applications, while the implementation covers only one environment for one application. This chapter describes the complete workload; the implementation scope is described in [Solution Scope](#solution-scope).*
 
-Oracle guides in planning, architecting, prototyping, and managing cloud migrations and disaster recovery solutions. Customers can move or protect critical workloads in weeks, or even days, instead of months by leveraging these included services.  
+Oracle provides guidance for planning, architecting, prototyping, and managing cloud migration and disaster recovery solutions. Customers can move or protect critical workloads in weeks, or even days, instead of months by using these services.
 
-Oracle will support in setting up the target OCVS architecture based on customer business and technical requirements.
+Oracle will support the design of the target Oracle Cloud VMware Solution architecture based on customer business and technical requirements.
 
-Oracle will move or protect selected VMs of the on-premise VMware to Oracle Cloud Infrastructure.
+Oracle will help move or protect selected virtual machines from the on-premises VMware environment to Oracle Cloud Infrastructure.
 
 __The objectives of this document are to:__
 
 
-Additionally, the these are the high-level goals for this document:
+The high-level goals for this document are:
 
-1.	Review together the existing on-premise architecture, map it to relevant Oracle OCI services, and propose a high-level tailored cloud architecture design.
+1.	Review the existing on-premises architecture, map it to relevant Oracle Cloud Infrastructure services, and propose a tailored high-level cloud architecture.
 
-2.	Provide the OCI architecture guidelines
+2.	Provide Oracle Cloud Infrastructure architecture guidance.
 
-3.	Address all OCVS-related aspects at security, network, compute, storage, and other levels for implementing the target cloud architecture.
+3.	Address Oracle Cloud VMware Solution design considerations across security, networking, compute, storage, operations, and related areas.
 
-4.	Set up the OCVS cloud environment according to the agreed design & architecture.
+4.	Define the Oracle Cloud VMware Solution cloud environment according to the agreed design and architecture.
 
-5.	Define the scope of the potential LIFT services.
+5.	Define the potential scope of Oracle Lift or related implementation services.
 
 ## Non-Functional Requirements
 <!--
@@ -259,13 +259,13 @@ PPM   | None
 
 *Guide:*
 
-*Describe the high-level technical requirements for the Workload. Consider all sub-chapters, but decide and choose which Non-Functional Requirements are necessary for your engagement. You might not need to capture all requirements for all sub-chapters.*
+*Describe the high-level technical requirements for the workload. Review all sub-chapters and keep only the non-functional requirement sections that are relevant to the engagement. Not every project needs requirements in every sub-chapter.*
 
-*This chapter is for describing customer-specific requirements (needs), not to explain Oracle solutions or capabilities.*
+*Use this chapter to describe customer-specific requirements and needs. Do not use it to explain Oracle solutions or capabilities.*
 
-The client wants to build a disaster recovery solution that will secure business-critical VMware workloads so that in the event of an on-premise data center failure, they can quickly recover IT services on OCI and OCVS.
+The client wants to build a disaster recovery solution for business-critical VMware workloads so that, in the event of an on-premises data center failure, IT services can be recovered quickly on Oracle Cloud Infrastructure and Oracle Cloud VMware Solution.
 
-### Regulations and Compliances Requirements
+### Regulatory and Compliance Requirements
 
 *Guide:*
 
@@ -274,11 +274,11 @@ The client wants to build a disaster recovery solution that will secure business
 *The Oracle Cloud Infrastructure Compliance Documents service lets you view and download compliance documents:
 https://docs.oracle.com/en-us/iaas/Content/ComplianceDocuments/Concepts/compliancedocsoverview.htm*
 
-*If there are none, then please state it. Leave the second sentence as a default in the document.*
+*If there are no regulatory or compliance requirements, state that clearly. Leave the second sentence as default text in the document.*
 
 *Example:*
 
-At the time of this document creation, no Regulatory and Compliance requirements have been specified.
+At the time this document was created, no regulatory or compliance requirements were specified.
 
 In addition to these requirements, the [CIS Oracle Cloud Infrastructure Foundation Benchmark, v1.2](https://www.cisecurity.org/benchmark/Oracle_Cloud) will be applied to the Customer tenancy.
 
@@ -286,9 +286,9 @@ In addition to these requirements, the [CIS Oracle Cloud Infrastructure Foundati
 
 *Guide:*
 
-*A diagram or list detailing all the required environments (e.g. development, text, live, production, etc.).*
+*Provide a diagram or list of all required environments, such as development, test, staging, and production.*
 
-*If you like to describe a current state, you can use or add the chapter 'Current Sate Architecture' before the 'Future State Architecture'.*
+*To describe the current state, add a 'Current State Architecture' chapter before 'Future State Architecture'.*
 
 
 Example:
@@ -306,74 +306,80 @@ Environment 3      |             | Sevilla     | Yes    | in Scope
 
 *This section captures the resilience and recovery requirements for the Workload. Note that these may be different from the current system.*
 
-*The Recovery Point Objective (RPO) and Recovery Time Objective (RTO) requirement of each environment should be captured in the environments section above, and wherever possible.*
+*Capture the Recovery Point Objective (RPO) and Recovery Time Objective (RTO) for each environment in the environments section above wherever possible.*
 
-- *What are the RTO and RPO requirements of the Application?*
+- *What are the application's RTO and RPO requirements?*
 - *What are the SLAs of the application?*
-- *What are the backup requirements*
+- *What are the backup requirements?*
 
-*Note that if needed, this section may also include an overview of the proposed backup and disaster recovery proposed architectures.*
+*If needed, this section may also include an overview of the proposed backup and disaster recovery architectures.*
 
-*This chapter is mandatory, while there could be no requirements on HA/DR, please mention that in a short single sentence.*
+*This chapter is mandatory. If there are no HA or DR requirements, state that in one short sentence.*
 
 *Example:*
 
-At the time of this document creation, no Resilience or Recovery requirements have been specified.
+At the time this document was created, no resilience or recovery requirements were specified.
 
 
-### Disaster recovery to OCVS
+### Disaster Recovery to OCVS
 
-This section describes the disaster recovery options and tools that will be used to protect selected workloads to OCVS. Below there are two examples of DR solutions that could be used to protect onpremises workloads to OCVS. HCX DR is included in   OCVS service and it provides basic DR capabilities. Another solution is VMware SRM that is more advanced solution licensed separately, not included in OCVS service. There are on the market also 3rd party solutions like Veeam, Rackware, Zerto and others which are not described in this document.
+This section describes the disaster recovery options and tools that can be used to protect selected workloads to Oracle Cloud VMware Solution. Bring Your Own License (BYOL) for Oracle Cloud VMware Solution is generally available and aligns Oracle Cloud VMware Solution with Broadcom's VMware Cloud Foundation (VCF) license portability model. Customers can use eligible VMware VCF subscription entitlements procured directly from Broadcom or an authorized partner when deploying and scaling Oracle Cloud VMware Solution environments on OCI.
+
+Oracle discontinued new long-term license-included Oracle Cloud VMware Solution SKUs, including monthly, 1-year, and 3-year license-included options, effective March 22, 2026. New SDDCs could be deployed using the license-included model until March 21, 2026, and existing SDDCs could continue scaling out with hourly license-included hosts until May 20, 2026. After these dates, all new Oracle Cloud VMware Solution capacity must be provisioned using BYOL. Existing license-included environments continue under their current commitment terms until they are transitioned to BYOL or the commitments expire. Customers must bring, procure, and maintain the VMware software licenses required for the SDDC and any disaster recovery tooling, according to the licensing terms agreed with Broadcom or an authorized VMware partner. This BYOL model must be validated during commercial and technical discovery.
+
+VMware HCX Disaster Recovery can provide basic virtual machine protection capabilities, but HCX DR has been deprecated by Broadcom and is planned for removal in a future HCX release. For enterprise disaster recovery and business continuity, VMware Site Recovery Manager, now part of the [VMware Live Recovery](https://www.vmware.com/products/cloud-infrastructure/advanced-services/live-recovery) portfolio, should be evaluated. VMware Site Recovery Manager automates and orchestrates failover, failback, and non-disruptive testing of virtual machines between sites to help minimize downtime and prevent data loss. Third-party solutions such as Zerto, RackWare, and Veeam can also be used where they better align with customer recovery objectives, operational model, or existing tooling.
 
 
 #### Disaster recovery architecture with VMware HCX
 
-HCX is an application mobility platform that allows you to migrate and protect VMs from an on-premises VMware environment to the OCVS SDDC. HCX Disaster recovery is a feature intended to protect virtual workloads managed by VMware vSphere that are either deployed in a private or a public cloud.
+VMware HCX is an application mobility platform that enables migration, workload rebalancing, and limited disaster recovery use cases for virtual machines between an on-premises VMware environment and an Oracle Cloud VMware Solution SDDC. HCX Disaster Recovery protects virtual workloads managed by VMware vSphere, whether those workloads are deployed in a private cloud or public cloud environment.
 
-The technical implementation of VMware HCX consists of the steps that are required to be performed at on-premises site and at the cloud site. The VMware HCX implementation and configuration at Oracle Cloud is taken care as part of the SDDC provisioning operation. Therefore, only minimum steps are required to be performed at Oracle Cloud side for successful implementation of VMware HCX.
+The VMware HCX implementation includes activities at both the on-premises site and the cloud site. The HCX Manager implementation and configuration in Oracle Cloud is handled as part of the Oracle Cloud VMware Solution SDDC provisioning process. As a result, only minimal Oracle Cloud-side configuration is required after provisioning; most remaining tasks are related to pairing, connectivity, service mesh configuration, and workload protection.
 
 The following image illustrates the solution overview for VMware HCX implementation with Oracle Cloud VMware Solution.
 
 ![OCVS DR Architecture using HCX](images/HCXarchitecture.png)
 
-HCX Disaster Recovery use the vSphere Replication technologies to transfer virtual machine disk data. When a virtual machine protection operation is first run, the replication engine performs a full synchronization of all the data that makes up the virtual machine to the target location datastore. Following that baseline synchronization, the system performs a delta synchronization, meaning that only changed data blocks are replicated.
+HCX Disaster Recovery uses VMware vSphere Replication technology to transfer virtual machine disk data. When protection is enabled for a virtual machine, the replication engine first performs a full synchronization of the virtual machine data to the target datastore. After the baseline synchronization completes, the system performs delta synchronizations, replicating only changed data blocks. Because HCX DR is deprecated, it should not be selected as the strategic disaster recovery platform for new enterprise designs unless the customer has explicitly accepted the lifecycle and support implications.
 
-Delta synchronisation occurs based on the recovery point objective (RPO) interval configured for the virtual machine, creating a replication instance. The selectable RPO ranges from 5 minutes to 24 hours. For example, setting the Recovery Point Objective (RPO) to 2 hours means that the maximum data loss that your organization can tolerate is 2 hours.
+Delta synchronization occurs according to the recovery point objective (RPO) configured for the virtual machine and creates a replication instance. The selectable RPO ranges from 5 minutes to 24 hours. For example, an RPO of 2 hours means the maximum tolerated data loss for that virtual machine is 2 hours.
 
 ##### Licensing
 
-The HCX comes with two different types of license, HCX Advanced included in OCVS service and the HCX Enterprise as an additional SKU which can be enabled from the OCI console on a monthly subscription basis.
+HCX licensing must be reviewed as part of the customer's VMware BYOL position. The licensing and entitlement model can vary by VMware software bundle, Oracle Cloud VMware Solution shape, and commercial agreement. Do not assume that HCX or other VMware components are license-included with Oracle Cloud VMware Solution.
 
-According to the feature requirements, the HCX license type should be carefully evaluated. For more details about the HCX licensing comparison, refer to the document link below.
+Evaluate the HCX license level against the required migration and mobility features before selecting an approach. For more information about HCX license differences, see the following documentation:
 
 [HCX License types](https://docs.oracle.com/en-us/iaas/Content/VMware/Concepts/ocvsoverview.htm#aboutsoftware__hcx-license-types)
 
 __Please note:__ According to [Broadcom’s official release notes for VMware HCX 4.11](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-11/hcx-4-11-release-notes/vmware-hcx-411-release-notes.html),
 the **HCX Disaster Recovery (HCX DR)** feature has been **deprecated** and is planned for removal in a future release.
 
-__Please note:__ If you are using OCVS with Standard Shapes, then the HCX enterprise is included in the subscription and no additional cost is required.
-
-__Please Note:__ Please check the VMware interoperability matrix for version compatibility of VMware HCX with the source vSphere environment.
+__Please note:__ Check the VMware interoperability matrix to confirm VMware HCX compatibility with the source vSphere environment.
 
 
 #### Disaster recovery architecture with VMware Site Recovery Manager
 
-VMware Site Recovery Manager is an extension to VMware vCenter that provides disaster recovery, site migration, and non-disruptive testing capabilities. It is more advanced solution in comparison to VMware HCX DR.
+VMware Site Recovery Manager is an enterprise-grade disaster recovery and business continuity solution for VMware environments. Site Recovery Manager is now part of the [VMware Live Recovery](https://www.vmware.com/products/cloud-infrastructure/advanced-services/live-recovery) portfolio and provides disaster recovery, site migration, and non-disruptive recovery testing capabilities. It provides more advanced orchestration than VMware HCX Disaster Recovery and should be evaluated as the preferred VMware-native disaster recovery option for enterprise workloads.
 
-Site Recovery Manager works in conjunction with VMware vSphere Replication to automate the process of migrating, recovering, testing, re-protecting, and failing-back virtual machine workloads.
+Site Recovery Manager works with VMware vSphere Replication to automate migration, recovery, testing, reprotection, and failback for virtual machine workloads.
 
-Migration of protected inventory and services from one site to the other is controlled by a recovery plan that specifies the order in which virtual machines are shut down and started up, the resource pools to which they are allocated, and the networks they can access.
+The migration or recovery of protected inventory and services from one site to another is controlled by a recovery plan. The recovery plan defines the order in which virtual machines are shut down and started, the resource pools to which they are assigned, and the networks they can access.
 
-Site Recovery Manager enables the testing of recovery plans, using a temporary copy of the replicated data, and isolated networks in a way that does not disrupt ongoing operations at either site.
+Site Recovery Manager enables non-disruptive recovery plan testing by using a temporary copy of replicated data and isolated networks. This allows recovery procedures to be validated without disrupting ongoing operations at either site.
 
- Multiple recovery plans can be configured to migrate individual applications and entire sites providing finer control over what virtual machines are failed over and failed back.
+Multiple recovery plans can be configured for individual applications or entire sites, providing granular control over which virtual machines are failed over and failed back.
 
-Site Recovery Manager extends the feature set of the virtual infrastructure platform to provide for rapid business continuity through partial or complete site failures.
+Site Recovery Manager extends the VMware virtual infrastructure platform to support business continuity during partial or complete site failures.
 
-High-level architecture of disaster recovery to OCVS with SRM.
+The following diagram shows a high-level architecture for disaster recovery to Oracle Cloud VMware Solution with Site Recovery Manager.
 
 ![High-level disaster recovery to OCVS with SRM](images/SRMDRtoOCVS.png)
 
+#### Third-party disaster recovery solutions
+
+Customers can also use third-party disaster recovery and cyber resilience platforms with Oracle Cloud VMware Solution where these tools meet the required RPO, RTO, operational, licensing, and support requirements. Examples include Zerto, RackWare, and Veeam. These solutions should be assessed during the solution design phase, including architecture fit, network requirements, replication behavior, failover and failback processes, testing approach, licensing, and vendor support boundaries.
+
 
 
 ### Security Requirements
@@ -388,18 +394,18 @@ High-level architecture of disaster recovery to OCVS with SRM.
 
 *Example:*
 
-At the time of this document creation, no Security requirements have been specified.
+At the time this document was created, no security requirements were specified.
 
 ### Networking Requirements
 
 *Guide*
 
-*Capture the Non-Functional Requirements for networking-related topics. You can use the networking questions in the [Annex](#networking-requirement-considerations)*
+*Capture the non-functional requirements for networking-related topics. You can use the networking questions in the [Annex](#networking-requirement-considerations).*
 
 
 *Example:*
 
-At the time of this document creation, no Networking requirements have been specified.
+At the time this document was created, no networking requirements were specified.
 
 ### Management and Monitoring
 
@@ -414,9 +420,9 @@ PPM   | None
 
 *Guide:*
 
-*The Workload Future State Architecture can be described in various forms. In the easiest case, we describe a Logical Architecture, possibly with a System Context Diagram. A high-level physical architecture is mandatory as a description of your solution.*
+*The workload future state architecture can be described in several forms. At minimum, describe the logical architecture, optionally with a system context diagram. A high-level physical architecture is mandatory.*
 
-*This should be the final architecture as part of the pre-sales solution, not an intermediate or draft version*
+*This should represent the final pre-sales solution architecture, not an intermediate or draft version.*
 
 *Additional architectures, in the subsections, can be used to describe needs for specific workloads.*
 
@@ -424,14 +430,14 @@ PPM   | None
 
 *Guide:*
 
-*Use this text for every engagement. Do not change. Aligned with the Cloud Adoption Framework*
+*Use this text for every engagement. Do not change it. This guidance is aligned with the Cloud Adoption Framework.*
 
 
 ### Naming Conventions
 
 *Guide:*
 
-*This chapter describes naming convention best practices and usually does not require any changes. If changes are required please refer to [Landing Zone GitHub](https://github.com/oracle-devrel/technology-engineering/tree/main/landing-zones). The naming convention zone needs to be described in the Solution Design by the service provider.*
+*This chapter describes naming convention best practices and usually does not require changes. If changes are required, refer to [Landing Zone GitHub](https://github.com/oracle-devrel/technology-engineering/tree/main/landing-zones). The service provider must describe naming conventions in the Solution Design.*
 
 *Use this template ONLY for new cloud deployments and remove it for brownfield deployments.*
 
@@ -440,33 +446,33 @@ PPM   | None
 
 *Guide:*
 
-*This chapter describes landing zone best practices and usually does not require any changes. If changes are required please refer to [Landing Zone GitHub](https://github.com/oracle-devrel/technology-engineering/tree/main/landing-zones). The full landing zone needs to be described in the Solution Design by the service provider.*
+*This chapter describes landing zone best practices and usually does not require changes. If changes are required, refer to [Landing Zone GitHub](https://github.com/oracle-devrel/technology-engineering/tree/main/landing-zones). The service provider must describe the full landing zone in the Solution Design.*
 
 *Use this template ONLY for new cloud deployments and remove it for brownfield deployments.*
 
 ```{.snippet}
 ar-landingzone
 ```
-All the above OCI and OCVS networking and security services and principles are implemented through the concept of a Landing Zone. The following diagram illustrates the Landing Zone reference architecture specific to the deployment of OCVS.
+The Oracle Cloud Infrastructure and Oracle Cloud VMware Solution networking and security services described above are implemented through a landing zone. The following diagram illustrates the landing zone reference architecture for Oracle Cloud VMware Solution.
 
 ![OCVS landing zone](images/Landing_zone.png)
 
-This architecture is designed specifically for Oracle Cloud VMware Solution which sits on top of the OCI core services such as Bare Metal Compute, and VCN networking. The architecture starts with the compartment design for the tenancy along with groups and policies for the segregation of duties.
+This architecture is designed specifically for Oracle Cloud VMware Solution, which runs on Oracle Cloud Infrastructure core services such as Bare Metal Compute and Virtual Cloud Network resources. The architecture starts with tenancy compartment design, groups, and policies to support segregation of duties.
 
-In Landing Zone, tenancy should have a dedicated compartment for VMware SDDC deployment. The existing tenancy can also be used but it is recommended to segregate the VMware SDDC environment from other OCI resources. The VMware SDDC Compartment is assigned a group with appropriate permissions for managing resources in the compartment and for accessing required resources in other compartments. As a best practice, it is recommended to create a dedicated compartment for VCN leveraged by the OCVS deployment to keep the networking resources completely separated in a dedicated compartment.
+In the landing zone, the tenancy should have a dedicated compartment for the VMware SDDC deployment. An existing tenancy can be used, but the VMware SDDC environment should be separated from other Oracle Cloud Infrastructure resources. The VMware SDDC compartment is assigned to a group with the permissions required to manage resources in that compartment and access required resources in other compartments. As a best practice, create a dedicated compartment for the VCN used by Oracle Cloud VMware Solution so networking resources are isolated in their own compartment.
 
-The VMware SDDC compartment will be utilised to deploy the SDDC service. The SDDC network compartment will host dedicated VCN resources to maintain the isolation of the VMware and network resources and thus use the IAM policies for network resource and access management. Oracle Cloud VMware Solution deployment workflow is a fully automated process and takes care of provisioning of required to compute & networking resources maintaining the security standard.
+The VMware SDDC compartment is used to deploy the SDDC service. The SDDC network compartment hosts the dedicated VCN resources required to isolate VMware and network resources, and IAM policies control network resource access and management. The Oracle Cloud VMware Solution deployment workflow is automated and provisions the required compute and networking resources while maintaining the expected security posture.
 
-The Landing Zone for OCVS includes pre-configured networking resources such as subnet, VLANs, Network Security Group, Security List, and Route Tables maintaining the security posture needed for enterprise VMware workloads. Also, it includes pre-configured Compute Bare Metal services required for VMware hypervisor operation. Additionally, VMware NSX as a Software Defined Networking is pre-configured but isolated in an overlay network zone.
+The Oracle Cloud VMware Solution landing zone includes preconfigured networking resources such as subnets, VLANs, network security groups, security lists, and route tables to support the security posture required for enterprise VMware workloads. It also includes the Bare Metal Compute resources required for VMware hypervisor operation. VMware NSX is configured as the software-defined networking layer and is isolated in an overlay network zone.
 
-Additional OCI services such as Cloud Guard, Events, Notifications, and WAF can be used to operate and monitor OCI resources for Oracle Cloud VMware Solutions such as OCI Compute, and OCI Network. The Notifications are set using Topics and Events for alerting administrators about changes in the deployed resources for this environment.
+Additional Oracle Cloud Infrastructure services such as Cloud Guard, Events, Notifications, and Web Application Firewall can be used to operate and monitor Oracle Cloud VMware Solution resources, including OCI Compute and OCI Networking resources. Notifications can be configured with topics and events to alert administrators about changes in deployed resources.
 
-__Please Note__ The VMware workloads can use limited OCI services when it comes to integration of VMware SDDC workloads to OCI.
-Low-level design of Landing zone with ${doc.customer.name}" relevant specific technical details will be provided during the architecture Design discovery process.
-The network for the SDDC network should not overlap with the existing networks in ${doc.customer.name}" tenancy. The SDDC can be scaled up to a maximum of 64 hosts with /21 SDDC CIDR range.
+__Please note:__ VMware workloads can integrate with selected Oracle Cloud Infrastructure services, subject to the design and connectivity model used for the VMware SDDC.
+The low-level landing zone design, including technical details specific to ${doc.customer.name}, will be provided during the architecture design discovery process.
+The SDDC network must not overlap with existing networks in the ${doc.customer.name} tenancy. With a /21 SDDC CIDR range, the SDDC can scale up to a maximum of 64 hosts.
 
-__Note:__ The table is a representation of the sample network layout for the /22 network however based on the SDDC CIDR range selected we can expect an automated network layout created by the SDDC provisioning operation with different network range for VLANS.
-SDDC workload CIDR will be identified as a part of the low-level design during the implementation.
+__Note:__ The following table shows a sample network layout for a /22 network. The actual VLAN network ranges are created automatically by the SDDC provisioning workflow and depend on the selected SDDC CIDR range.
+The SDDC workload CIDR will be identified as part of the low-level design during implementation.
 
 
 | VLAN Name                   | CIDR Range    |
@@ -496,9 +502,9 @@ PPM   | None
 
 *Guide:*
 
-*Provide a high-level logical Oracle solution for the complete Workload. Indicate Oracle products as abstract groups, and not as physical detailed instances. Create an architecture diagram following the latest notation and describe the solution.*
+*Provide a high-level logical Oracle solution for the complete workload. Represent Oracle products as abstract groups rather than detailed physical instances. Create an architecture diagram using the latest notation and describe the solution.*
 
-*To implement a solution the Physical Architecture is needed in the next chapter. The physical notation can show individual components with physical attributes such as IP addresses, hostnames, or sizes.*
+*To implement the solution, provide the physical architecture in the next chapter. The physical architecture can show individual components with physical attributes such as IP addresses, hostnames, and sizes.*
 
 *[The Oracle Cloud Notation, OCI Architecture Diagram Toolkits](https://docs.oracle.com/en-us/iaas/Content/General/Reference/graphicsfordiagrams.htm)*
 
@@ -513,9 +519,9 @@ PPM   | None
 
 *Guide:*
 
-*The Workload Architecture is typically described in a physical form. This should include all solution components. You do not have to provide solution build or deployment details such as IP addresses.*
+*The workload architecture is typically described in physical form and should include all solution components. You do not need to provide detailed build or deployment information such as IP addresses.*
 
-*Please describe the solution with an architecture image plus a written text. If you have certain specifics you like to explain, you can also use the Solution Consideration chapter to describe the details there.*
+*Describe the solution with an architecture diagram and supporting text. If specific design decisions require more detail, describe them in the Solution Considerations chapter.*
 
 *[The Oracle Cloud Notation, OCI Architecture Diagram Toolkits](https://docs.oracle.com/en-us/iaas/Content/General/Reference/graphicsfordiagrams.htm)*
 
@@ -526,46 +532,50 @@ PPM   | None
 *Example:*
 
 
-The future state architecture covers the current on-premises workloads to be hosted on Oracle Cloud VMware Solution(OCVS). The OCVS is deployed at the Availability Domain (AD) in the OCI region and spans across 3 Fault Domains (FD) in the region.
-The OCI Bare Metal (BM) instances utilized by the service are spread across the Fault Domain (FD) in a round-robin fashion offering complete redundancy to the OCVS workloads.
-The OCVS comes with two distinct architectures as represented below.
-- OCVS with DenseIO server - This architecture primarily uses vSAN Storage leveraging NVMe drives from the local Bare Metal (BM) servers.
-- OCVS with Standard Shapes - This architecture is completely based on the OCI Block Storage as a primary storage option for the VM workloads.
+The future state architecture covers the current on-premises workloads that will be hosted on Oracle Cloud VMware Solution. Oracle Cloud VMware Solution is deployed in an availability domain within the selected Oracle Cloud Infrastructure region and spans three fault domains in that region.
+The OCI Bare Metal instances used by the service are distributed across fault domains in a round-robin pattern to provide redundancy for Oracle Cloud VMware Solution workloads.
+Oracle Cloud VMware Solution supports two primary architecture options:
+- Oracle Cloud VMware Solution with DenseIO shapes: This architecture primarily uses VMware vSAN storage backed by NVMe drives from the local Bare Metal servers.
+- Oracle Cloud VMware Solution with Standard Shapes: This architecture uses OCI Block Storage as the primary storage option for virtual machine workloads.
+
+Oracle Cloud VMware Solution requires customer-provided VMware software licensing under a BYOL model for new capacity. The customer is responsible for bringing, procuring, registering, allocating, and maintaining the VMware licenses required for the selected SDDC architecture, including any additional VMware disaster recovery or business continuity components. Eligible VMware VCF subscription entitlements are registered in Oracle Cloud VMware Solution License Management, allocated to the target OCI region, and selected during SDDC provisioning, workload cluster creation, or ESXi host scale-out. License eligibility, portability, support, and commercial terms must be validated with Broadcom or an authorized VMware partner before implementation.
 
 ![Future State Architecture](images/ocvs-overview.png)
 
-Oracle Cloud VMware Solution is the central part of this deployment and provides a fully automated implementation of a VMware software-defined data center (SDDC) within your Oracle Cloud Infrastructure tenancy. The solution runs on Oracle Cloud Infrastructure Bare Metal Compute and contains the following VMware components:
+Oracle Cloud VMware Solution is the central component of this deployment. It provides an automated implementation of a VMware software-defined data center (SDDC) within the customer's Oracle Cloud Infrastructure tenancy. The solution runs on Oracle Cloud Infrastructure Bare Metal Compute and includes the following VMware components:
 
 * VMware vSphere Hypervisor (ESXi)
 * VMware vCenter Server
 * VMware vSAN
 * OCI Block Storage
 * VMware NSX-T
-* VMware HCX Advanced
+* VMware HCX, subject to customer licensing and entitlement
 
 
 
-The architecture has the following components:
+The architecture includes the following components:
 
 __OCVS__
 
-The __VMware SDDC__ - consists of vSphere (ESXi + vCenter), NSX-T, vSAN & HCX. The SDDC deployment can be on OCI DenseIO shapes that offer vSAN Storage or it can be on OCI Standard Shape with OCI Block Storage as a primary storage option.  
+The __VMware SDDC__ consists of vSphere (ESXi and vCenter), NSX-T, vSAN, and HCX. The SDDC can be deployed on OCI DenseIO shapes that provide vSAN storage, or on OCI Standard Shapes with OCI Block Storage as the primary storage option.
+
+* __VMware licensing__ - New Oracle Cloud VMware Solution capacity is consumed with customer-provided VMware licenses under the BYOL model. The solution design must confirm the VMware Cloud Foundation, vSphere, vSAN, NSX, HCX, VMware Live Recovery, Site Recovery Manager, or other VMware entitlements required for the selected architecture and recovery approach. It must also confirm that the required VCF license allocations are registered in Oracle Cloud VMware Solution License Management and available in the target OCI region before provisioning or scale-out.
 
-* __VMware HCX__ - Application mobility platform designed for simplifying application migration, workload re-balancing, and business continuity across data centers and clouds. This will allow the seamless migration of VMware workloads to OCVS.
+* __VMware HCX__ - An application mobility platform designed to simplify application migration and workload rebalancing across data centers and clouds. HCX can support selected mobility use cases for VMware workloads to Oracle Cloud VMware Solution, subject to licensing, entitlement, compatibility, and lifecycle considerations.
 
-* __HCX Manager__ – HCX manager is an appliance deployed in Oracle Cloud VMware Solution. HCX manager will be paired with an on-premises vCenter through HCX Connector.  
+* __HCX Manager__ - An appliance deployed in Oracle Cloud VMware Solution. HCX Manager is paired with the on-premises vCenter through HCX Connector.
 
-* __HCX Connector__ – HCX connector is an appliance deployed at an on-premises vCenter server which will be then paired with the HCX manager in the cloud for the base configuration necessary for workload migration.  
+* __HCX Connector__ - An appliance deployed with the on-premises vCenter Server and paired with HCX Manager in the cloud to provide the base configuration required for workload migration.
 
-* __VMware NSX-T__ - This is NSX-T Data Center implementation as part of the SDDC stack used for Software Defined Networking. The migrated workloads can use NSX network segments for networking usage. NSX-T offers full perimeter services configuration in OCVS environments such as Load Balancer, Routing, Switching, firewall, and micro-segmentation.
+* __VMware NSX-T__ - The NSX-T Data Center implementation that provides software-defined networking for the SDDC stack. Migrated workloads can use NSX network segments. NSX-T provides networking and security services for Oracle Cloud VMware Solution environments, including load balancing, routing, switching, firewalling, and micro-segmentation.
 
-* __VMware vSAN__ - VMware vSAN is a software-defined storage solution offered as part of the OCVS SDDC solution. The vSAN has been configured by leveraging locally attached NVMe all-flash disks from each OCI Bare Metal server to offer common storage for workloads.
+* __VMware vSAN__ - A software-defined storage solution included with the Oracle Cloud VMware Solution SDDC. vSAN uses locally attached NVMe all-flash disks from each OCI Bare Metal server to provide shared storage for workloads.
 
-* __OCI Block Storage__ - The OCI Block storage can be leveraged as an additional storage option with DenseIO compute SDDC along with vSAN. The Standard Shape OCVS environment consists of OCI block storage as the only primary storage option.
+* __OCI Block Storage__ - OCI Block Storage can be used as additional storage with a DenseIO SDDC alongside vSAN. In a Standard Shape Oracle Cloud VMware Solution environment, OCI Block Storage is the primary storage option.
 
-* __VMware vSphere__ - Includes ESXi and vCenter servers
+* __VMware vSphere__ - Includes ESXi hosts and vCenter Server.
 
-* __FastConnect__ - OCI FastConnect is a dedicated private high-speed network link connected to ${doc.customer.name} Data Center and OCI region. The FastConnect will be leveraged for migrating the workloads over the network.
+* __FastConnect__ - Oracle Cloud Infrastructure FastConnect is a dedicated, private, high-speed network connection between the ${doc.customer.name} data center and the selected Oracle Cloud Infrastructure region. FastConnect can be used to migrate workloads over the network.
 
 
 ## Solution Considerations
@@ -582,42 +592,42 @@ PPM   | None
 
 *Guide:*
 
-*Describe certain aspects of your solution in detail. What are the security, resilience, networking, and operations decisions you have taken that are important for your customer?*
+*Describe important solution decisions in detail, including security, resilience, networking, and operations decisions that are relevant to the customer.*
 
 ### High Availability and Disaster Recovery
 
 *Reference:*
 
-- [Resilliance on OCI](https://docs.public.oneportal.content.oci.oraclecloud.com/en-us/iaas/Content/cloud-adoption-framework/era-resiliency.htm)
+- [Resilience on OCI](https://docs.public.oneportal.content.oci.oraclecloud.com/en-us/iaas/Content/cloud-adoption-framework/era-resiliency.htm)
 - [Workload Related Content](https://github.com/oracle-devrel/technology-engineering/)
 #### OCVS Resilience and Recovery
 
-Oracle Cloud VMware Solution is deployed at Availability Domain (AD) within the OCI region. Each Availability domain consists of Fault Domains to maintain a fault-tolerant and highly resilient environment. For more details about OCI Availability domains and Fault Domains refer to the [OCI documentation](https://docs.oracle.com/en-us/iaas/Content/General/Concepts/regions.htm).
+Oracle Cloud VMware Solution is deployed in an availability domain within the selected Oracle Cloud Infrastructure region. Each availability domain contains fault domains that support fault-tolerant and resilient designs. For more information about OCI availability domains and fault domains, see the [OCI documentation](https://docs.oracle.com/en-us/iaas/Content/General/Concepts/regions.htm).
 
-The details of the Oracle Cloud Infrastructure SLAs are found in the link below.
+Details of the Oracle Cloud Infrastructure SLAs are available at the following link:
 [OCI Service SLA](https://www.oracle.com/ae/cloud/sla/).
 
 ##### OCVS High Availability
-This section describes the VMware SDDC High Availability.
+This section describes VMware SDDC high availability.
 
-__OCI BM Compute (ESXi):__ The OCI native services such as compute bare metal and VCN resources are highly resilient cloud service offerings from Oracle Cloud Infrastructure. OCI BM failure can be addressed by replacing the faulty node with a new ESXi host in the cluster.
+__OCI Bare Metal Compute (ESXi):__ OCI native services such as Bare Metal Compute and VCN resources are resilient cloud services. An OCI Bare Metal host failure can be addressed by replacing the faulty node with a new ESXi host in the cluster.
 
-__OCI BM NVMe (vSAN):__ The OCVS SDDC consist of vSAN for the software-defined storage layer. With vSAN's failure to tolerate (FTT) feature, host failures, and data loss can be effectively managed. Customers can utilize the vSAN SPBM (Storage Policy Based Management) which includes different RAID levels to protect the data.
+__OCI Bare Metal NVMe (vSAN):__ The Oracle Cloud VMware Solution SDDC uses vSAN for the software-defined storage layer. vSAN failure to tolerate (FTT) policies help manage host failures and reduce the risk of data loss. Customers can use vSAN Storage Policy Based Management, including different RAID levels, to protect data.
 
-__OCVS Networking (NSX-T):__ The OCVS SDDC consists of NSX-T implementation to manage software-defined networking. The NSX Edge, Managers/Controllers are deployed in a fully redundant manner to maintain high availability.
+__OCVS Networking (NSX-T):__ The Oracle Cloud VMware Solution SDDC uses NSX-T to manage software-defined networking. NSX Edge nodes and NSX Managers are deployed redundantly to maintain high availability.
 
-__OCI Block Storage:__ The OCI Block Storage offers the highest level of data resiliency by the backend system at the availability domain. The OCI Block storage being the primary storage option with OCVS does not require RAID configuration but rather relies on the resiliency offered by the Oracle Cloud Infrastructure.
+__OCI Block Storage:__ OCI Block Storage provides backend data resiliency within the availability domain. When OCI Block Storage is used as the primary storage option with Oracle Cloud VMware Solution, RAID configuration is not required at the VMware layer; the design relies on the resiliency provided by Oracle Cloud Infrastructure.
 
 
 ### Security
 
 *Guide:*
 
-*Please describe your solution from a security point of view. Generic security guidelines are in the Annex chapter.*
+*Describe the solution from a security point of view. Generic security guidelines are provided in the Annex chapter.*
 
 *Example:*
 
-Please see our security guidelines in the [Annex](#security-guidelines).
+See the security guidelines in the [Annex](#security-guidelines).
 Oracle employs best-in-class, enterprise-grade security technology, and operational processes to secure cloud services. To deploy and operate your workloads securely in Oracle Cloud, you must be aware of your security and compliance responsibilities.
 
 Oracle ensures the security of cloud infrastructure and operations, such as cloud operator access controls and infrastructure security patching. You’re responsible for configuring your cloud resources securely. The following graphic illustrates the shared security responsibility model.  
@@ -642,41 +652,41 @@ The shared responsibility extends across different domains including identity ma
 
 #### OCVS Security Posture
 
-The section below describes the security posture of Oracle Cloud VMware Solution and Oracle Cloud Infrastructure.
+The section below describes the security posture for Oracle Cloud VMware Solution and Oracle Cloud Infrastructure.
 
-* Access to the Customer's OCI tenancy is restricted and controlled using IAM and IDCS federations. Network sources can be optionally used to restrict access from known IP addresses within VCN or on-premises.
+* Access to the customer's OCI tenancy is restricted and controlled using IAM and identity federation. Network sources can optionally restrict access to known IP addresses from a VCN or on-premises network.
 
-* Security in a subnet can be controlled by Security Lists and/or Network Security Groups. OCI is a zero-trust environment by default, you must explicitly permit traffic for known communication patterns. Additional security can be offered to Customer's external facing applications using OCI Web Application Firewall.
+* Subnet security can be controlled by security lists and network security groups. OCI follows a zero-trust model by default, so traffic must be explicitly allowed for known communication patterns. OCI Web Application Firewall can provide additional protection for customer-facing applications.
 
-* VLAN resides in VCN and is only provisioned for OCVS service. Each VLAN is attached to the Network Security Group to control traffic. All traffic inside a VLAN is blocked by default.
+* VLANs reside in the VCN and are provisioned for the Oracle Cloud VMware Solution service. Each VLAN is attached to a network security group to control traffic. Traffic within a VLAN is blocked by default until required rules are configured.
 
-* An NSX Segment is an overlay network that runs on top of the VMware virtualization stack. This network is independent outside of the VCN network. Any communication from the NSX overlay segment to OCI resources needs to be explicitly allowed through uplink interfaces using routing and controlled using security lists.
+* An NSX segment is an overlay network that runs on top of the VMware virtualization stack. This network is independent of the VCN network. Communication from an NSX overlay segment to OCI resources must be explicitly allowed through uplink interfaces, routing, and security rules.
 
-* Security in an NSX Segment is managed by the NSX-T control plane, by default all traffic inside a segment is allowed. The NSX Micro-Segmentation enables you to increase the agility and efficiency of your network infrastructure while maintaining the highest level of security posture.
+* Security within an NSX segment is managed by the NSX-T control plane. By default, traffic inside a segment is allowed. NSX micro-segmentation can improve network agility and operational efficiency while maintaining a strong security posture.
 
-* Users from an on-premises environment can securely connect to Oracle Cloud VMware Solution resources through IPSec and or FastConnect.
+* Users from an on-premises environment can securely connect to Oracle Cloud VMware Solution resources through IPSec VPN or FastConnect.
 
-* Bastion host is deployed in a public subnet in Customer's tenancy. Secured access is allowed for Remote Desktop Protocol (RDP) through Internet Gateway and controlled using a security list.
+* A bastion host can be deployed in a public subnet in the customer's tenancy. Secure Remote Desktop Protocol (RDP) access is allowed through an internet gateway and controlled by security rules.
 
-* The OCVS SDDC environment is allowed to access only from the Bastion host.
+* Access to the Oracle Cloud VMware Solution SDDC environment should be allowed only from approved administrative entry points, such as the bastion host.
 
 #### OCVS Data Security
 
-This section details Data Security for the virtual machines in the OCVS environment. It also provides details about how encryption works in vSAN and possible options for Data at rest and Data at transit. We have not received any data security requirements from the Customer. Therefore, the below section details out-of-the-box data security standards for OCVS.
+This section describes data security for virtual machines in the Oracle Cloud VMware Solution environment. It explains how encryption works with vSAN and outlines options for data at rest and data in transit. If no customer-specific data security requirements have been received, this section describes the default data security capabilities available with Oracle Cloud VMware Solution.
 
 __vSAN Data-At-Rest__
 
-Oracle Cloud VMware Solution uses VMware vSAN technology for virtual machine storage management. vSAN comes with its own data-at-rest encryption technique. vSAN can encrypt data at rest in the vSAN datastore. Data at rest encryption within vSAN requires an external Key Management Server (KMS) or a vSphere Native Key Provider.
-vSAN data at rest encryption is out of the scope of this project. However, customers can enable the data-at-rest encryption anytime at cluster provided it meets the required pre-requisite.
+Oracle Cloud VMware Solution uses VMware vSAN technology for virtual machine storage management. vSAN provides data-at-rest encryption for data stored in the vSAN datastore. vSAN data-at-rest encryption requires an external Key Management Server (KMS) or a vSphere Native Key Provider.
+vSAN data-at-rest encryption is out of scope for this project. However, customers can enable data-at-rest encryption at the cluster level later, provided the required prerequisites are met.
 
 __vSAN Data-in-Transit__
 
-Oracle Cloud VMware Solution uses VMware vSAN technology for virtual machine storage management. vSAN can encrypt data in transit, as it moves across hosts in your vSAN cluster. vSAN can encrypt data in transit across hosts in the cluster. When you enable data-in-transit encryption, vSAN encrypts all data and metadata traffic between hosts. Traffic between data hosts and witness hosts is encrypted.
-vSAN data encryption in transit is out of the scope of this project. However, the Customer can enable this functionality at the vSAN cluster in OCVS SDDC.
+Oracle Cloud VMware Solution uses VMware vSAN technology for virtual machine storage management. vSAN can encrypt data in transit as it moves between hosts in the vSAN cluster. When data-in-transit encryption is enabled, vSAN encrypts all data and metadata traffic between hosts. Traffic between data hosts and witness hosts is also encrypted.
+vSAN data-in-transit encryption is out of scope for this project. However, the customer can enable this capability at the vSAN cluster level in the Oracle Cloud VMware Solution SDDC.
 
 __Block Storage Encryption__
 
-OCI Block Storage can be used to scale the storage for DenseIO OCVS deployment and be used as primary storage in the case of Standard Shapes OCVS. OCI Block Volume is presented to the VMware ESXi server as an iSCSI target to store virtual machine files. OCI security features such as KMS, encryption, and vaults apply to VM data stored in OCI Block Volume. OCI Block Volume is mounted as an external Datastore for VMware SDDC by leveraging OCI managed/Customer managed keys for VM data encryption.
+OCI Block Storage can be used to scale storage for DenseIO Oracle Cloud VMware Solution deployments and as primary storage for Standard Shape Oracle Cloud VMware Solution deployments. OCI Block Volumes are presented to VMware ESXi hosts as iSCSI targets for storing virtual machine files. OCI security features such as Key Management, encryption, and Vault apply to virtual machine data stored on OCI Block Volumes. OCI Block Volumes are mounted as external datastores for the VMware SDDC and can use Oracle-managed or customer-managed keys for virtual machine data encryption.
 
 ### Networking
 
@@ -688,30 +698,30 @@ network-solution-considerations-guide
 
 *Reference:*
 
-*A list of possible Oracle solutions can be found in the [Annex](#networking-solutions).*
+*A list of possible Oracle solutions is available in the [Annex](#networking-solutions).*
 
 *Example:*
 
 ```{.snippet}
 network-solution-firewall
 ```
-The architecture has the following components:
+The architecture includes the following components:
 
-* __On-premises Network__ - This network is the local network used by your organization. It is one of the spokes of the topology.
+* __On-premises Network__ - The local network used by the organization. It is one of the spokes in the topology.
 
-* __Region__ - An Oracle Cloud Infrastructure region is a localized geographic area that contains one or more data centers, called availability domains. Regions are independent of other regions, and vast distances can separate them (across countries or even continents).
+* __Region__ - An Oracle Cloud Infrastructure region is a localized geographic area that contains one or more data centers, called availability domains. Regions are independent from one another and can be separated by large geographic distances.
 
-* __Virtual Cloud Network (VCN)__ - A VCN is a customizable, private network that you set up in an Oracle Cloud Infrastructure region. Like traditional data center networks, VCNs give you complete control over your network environment. You can segment VCNs into subnets, which can be scoped to a region or an availability domain. Both regional subnets and availability domain-specific subnets can coexist in the same VCN. A subnet can be public or private.
+* __Virtual Cloud Network (VCN)__ - A customizable private network in an Oracle Cloud Infrastructure region. Like traditional data center networks, VCNs provide control over the network environment. VCNs can be segmented into subnets that are regional or availability domain-specific. Both subnet types can coexist in the same VCN, and each subnet can be public or private.
 
-* __Security List__ - For each subnet, you can create security rules that specify the source, destination, and type of traffic that must be allowed in and out of the subnet.
+* __Security List__ - A set of subnet-level security rules that specify the source, destination, and type of traffic allowed into and out of the subnet.
 
 * __Network Security Group (NSG)__ - NSGs act as virtual firewalls for your cloud resources. With the zero-trust security model of Oracle Cloud Infrastructure, all traffic is denied, and you can control the network traffic inside a VCN. An NSG consists of a set of ingress and egress security rules that apply to only a specified set of VNICs in a single VCN.
 
-* __Route Table__ - Route tables contain rules to route traffic from subnets to destinations outside a VCN, typically through gateways.
+* __Route Table__ - A set of rules that routes traffic from subnets to destinations outside a VCN, typically through gateways.
 
-* __Dynamic Routing Gateway (DRG)__ - The DRG is a virtual router that provides a path for private network traffic between a VCN and a network outside the region, such as a VCN in another Oracle Cloud Infrastructure region, an on-premises network, or a network in another cloud provider.
+* __Dynamic Routing Gateway (DRG)__ - A virtual router that provides a private network path between a VCN and networks outside the region, such as another OCI region, an on-premises network, or another cloud provider.
 
-* __Bastion Host__ - The bastion host is a compute instance that serves as a secure, controlled entry point to the topology from outside the cloud. The bastion host is provisioned typically in a demilitarized zone (DMZ). It enables you to protect sensitive resources by placing them in private networks that can't be accessed directly from outside the cloud. The topology has a single, known entry point that you can monitor and audit regularly. So, you can avoid exposing the more sensitive components of the topology without compromising access to them.
+* __Bastion Host__ - A compute instance that provides a secure, controlled administrative entry point from outside the cloud. The bastion host is typically provisioned in a demilitarized zone (DMZ). It helps protect sensitive resources by keeping them in private networks that cannot be accessed directly from outside the cloud. This gives the topology a known entry point that can be monitored and audited.
 
 * __VPN Connect__ - VPN Connect provides site-to-site IPSec VPN connectivity between your on-premises network and VCNs in Oracle Cloud Infrastructure. The IPSec protocol suite encrypts IP traffic before the packets are transferred from the source to the destination and decrypts the traffic when it arrives.
 
@@ -725,48 +735,48 @@ The following diagram of a reference architecture shows how to set up a Virtual
 
 ![IPSec VPN](images/vpn.png)
 
-IPSec VPN architecture has the following components:
+The IPSec VPN architecture includes the following components:
 
-* __VPN Connect__ - Function that manages IPSec VPN connections to your tenancy.
+* __VPN Connect__ - The OCI service function that manages IPSec VPN connections to the tenancy.
 
-* __Customer-Premises Equipment (CPE)__ - An object that represents the network asset that lives in the on-premises network and establishes the VPN connection. Most border firewalls act as the CPE, but a separate device (like an appliance or a server) can be a CPE.
+* __Customer-Premises Equipment (CPE)__ - An object that represents the network asset in the on-premises network that establishes the VPN connection. Most border firewalls can act as the CPE, but a separate appliance or server can also be used.
 
 * __Internet Protocol Security (IPSec)__ - A protocol suite that encrypts IP traffic before packets are transferred from the source to the destination.
 
-* __Tunnel__ - Each connection between the CPE and Oracle Cloud Infrastructure.
+* __Tunnel__ - A connection between the CPE and Oracle Cloud Infrastructure.
 
-* __Border Gateway Protocol (BGP) routing__ - Allows routes to be learned dynamically. The DRG dynamically learns the routes from your on-premises network. On the Oracle side, the DRG advertises the VCN's subnets.
+* __Border Gateway Protocol (BGP) routing__ - Enables dynamic route learning. The DRG dynamically learns routes from the on-premises network and advertises the VCN subnets from the Oracle side.
 
-* __Static Routing__ - When you create the VPN connection, you inform the existing networks on each side. Changes are not learned dynamically.
+* __Static Routing__ - Requires the networks on each side of the VPN connection to be defined manually. Route changes are not learned dynamically.
 
-IPSec VPN will be used to provide for the connection between ${doc.customer.name}" data center and Oracle OCI Public cloud region for standard day-to-day operational purposes. Based on the current information IPSec connection is already established.
+IPSec VPN will provide connectivity between the ${doc.customer.name} data center and the Oracle Cloud Infrastructure region for standard day-to-day operational purposes. Based on the current information, the IPSec connection is already established.
 
-##### Fast Connect
+##### FastConnect
 
 The following reference architecture diagram shows how to set up a FastConnect connection between your on-premises network and Virtual Cloud Network (VCN).
 
-![Fast Connect](images/fc.png)
+![FastConnect](images/fc.png)
 
-* __Border Gateway Protocol (BGP) routing__ - Allows routes to be learned dynamically. The DRG dynamically learns the routes from your on-premises network. On the Oracle side, the DRG advertises the VCN's subnets.
+* __Border Gateway Protocol (BGP) routing__ - Enables dynamic route learning. The DRG dynamically learns routes from the on-premises network and advertises the VCN subnets from the Oracle side.
 
 * __Private Peering__ - Extends existing infrastructure by using private IP addresses.
 
 * __Public Peering__ - Allows public Oracle Cloud Infrastructure services to be accessed using a private connection instead of the internet.
 
-* __Virtual Circuit__ - The private path used to connect on-premises and Oracle Cloud Infrastructure. It can include multiple lines, physical or logical, depending on the requirements and capabilities of the line provider.
+* __Virtual Circuit__ - The private path used to connect on-premises environments and Oracle Cloud Infrastructure. It can include multiple physical or logical lines, depending on the requirements and the provider's capabilities.
 
-Fast Connect will be used to provide for the connection between ${doc.customer.name}" data center and Oracle OCI Frankfurt cloud region for the period migrations of VMs from on-premise to Oracle cloud.  It is a requirement to use Fast Connect at least for the period of workload migration.
+FastConnect will provide connectivity between the ${doc.customer.name} data center and the selected Oracle Cloud Infrastructure region during virtual machine migration from on-premises VMware to Oracle Cloud. FastConnect is required at least for the duration of workload migration.
 
 ##### OCVS Specific Networking Configuration Within OCI
 
-The Oracle Cloud VMware Solution networking categorises into Virtual Cloud Networks, Subnets, and VLANs. Each VLAN within VCN is attached to the Network Security Group for network communication and Route Table for routing functionality. Similarly, the subnet created as an outcome of the SDDC provisioning operation is attached to Security List and Route Table.
+Oracle Cloud VMware Solution networking is organized into virtual cloud networks, subnets, and VLANs. Each VLAN within the VCN is attached to a network security group for traffic control and a route table for routing. Similarly, the subnet created during the SDDC provisioning workflow is attached to a security list and route table.
 
 ![OCVS detailed networking overview and components](images/net_overview.png)
 
 ##### OCI Virtual Cloud Network (VCN) for OCVS
 
-All the resources in OCVS/SDDC architecture are in a single VCN.
-For VMware SDDC we need at least /24 network CIDR but recommended is to have a dedicated /16 VCN CIDR block that can accommodate future scaling of the networks.
+All Oracle Cloud VMware Solution SDDC resources are deployed in a single VCN.
+A VMware SDDC requires at least a /24 network CIDR. A dedicated /16 VCN CIDR block is recommended to support future network growth.
 
 | VCN                      | CIDR Range              |
 |:-------------------------|:------------------------|
@@ -774,7 +784,7 @@ For VMware SDDC we need at least /24 network CIDR but recommended is to have a d
 | SDDC CIDR                | 10.0.0.0/21             |
 | Workload CIDR (Optional) | 192.168.10.0/24 (NSX-T) |
 
-The OCVS networking resources such as Subnet, VLANs, Network Security Groups (NSG), Route Tables, and Gateways are the result of OCVS SDDC provisioning operation. The network CIDR ranges for the management VLANs are solely dependent on the size of the SDDC CIDR. The network design considerations should be carefully assessed before provisioning the OCVS environment.
+Oracle Cloud VMware Solution networking resources, including subnets, VLANs, network security groups, route tables, and gateways, are created as part of the SDDC provisioning workflow. The CIDR ranges for management VLANs depend on the size of the SDDC CIDR. Network design considerations should be assessed carefully before provisioning the Oracle Cloud VMware Solution environment.
 
 ### Manageability and Observability
 
@@ -792,17 +802,17 @@ Price Lists and SKUs / Part Numbers: https://esource.oraclecorp.com/sites/eSourc
 
 *Guide:*
 
-*Estimate and size the physically needed resources of the Workload. The information can be collected and is based upon previously gathered capacities, business user numbers, integration points, or translated existing on-premises resources. The sizing is possibly done with or even without a Physical Architecture. It is okay to make assumptions and to clearly state them!*
+*Estimate and size the physical resources required for the workload. This information can be based on existing capacity data, business user volumes, integration points, or translated on-premises resource usage. Sizing can be completed with or without a finalized physical architecture. Clearly state all assumptions.*
 
-*Clarify with sales your assumptions and your sizing. Get your sales to finalize the BoM with discounts or other sales calculations. Review the final BoM and ensure the sales are using the correct product SKUs / Part Number.*
+*Review sizing assumptions with Sales. Ask Sales to finalize the BoM with discounts or other commercial calculations. Review the final BoM and confirm that the correct product SKUs and part numbers are used.*
 
-*Even if the BoM and sizing were done with the help of Excel between the different teams, ensure that this chapter includes or links to the final BoM as well.*
+*Even if the BoM and sizing were prepared in Excel by different teams, ensure that this chapter includes or links to the final BoM.*
 
 <!--                                                 -->
 <!-- End of 3) Workload Requirements and Architecture -->
 <!--                                                 -->
 
-<!-- Use the below chapter only for Oracle Implementations such as Lift and FastStart. do not describe the work plan for 3rd Party implementation partners -->
+<!-- Use the below chapter only for Oracle implementations such as Lift and FastStart. Do not describe the work plan for third-party implementation partners. -->
 
 
 # Project Implementation (Only for Oracle Implementations!)
@@ -820,7 +830,7 @@ PPM   | None
 
 *Guide:*
 
-*A scope disclaimer should limit scope changes and create awareness that a change of scope needs to be agreed upon by both parties.*
+*A scope disclaimer should limit scope changes and make clear that any scope change must be agreed by both parties.*
 
 *Example:*
 
@@ -839,7 +849,7 @@ PPM   | C
 
 *Guide:*
 
-*Describe the scope of the implementation as a sub-set of the Workload scope. For example one environment from one application.*
+*Describe the implementation scope as a subset of the workload scope. For example, the implementation might include one environment for one application.*
 
 *Example:*
 
@@ -858,7 +868,7 @@ PPM   | C
 
 *Guide:*
 
-*What's the value for the customer to do an Oracle implementation? For example, speed of deployment and the resulting impact on time to market, and free service. Do not describe Oracle's value or consumption.*
+*Describe the customer value of an Oracle-led implementation, such as deployment speed, reduced time to market, or access to eligible free services. Do not describe Oracle's internal value or consumption goals.*
 
 *Example:*
 
@@ -877,17 +887,17 @@ PPM   | C
 
 *Guide:*
 
-*Technical success criteria for the implementation. As always be S.M.A.R.T: Specific, Measurable, Achievable, Relevant, Timebound. Example: 'Deployment of all OCI resources for the scoped environments in 3 months'.*
+*Define technical success criteria for the implementation. Success criteria should be SMART: specific, measurable, achievable, relevant, and time-bound. Example: 'Deploy all OCI resources for the scoped environments within 3 months'.*
 
 *Example:*
 
-The below-listed success criteria are for the ${doc.config.impl.type} implementation only. Partner activities and success criteria are not listed in this documentation.
+The success criteria listed below apply only to the ${doc.config.impl.type} implementation. Partner activities and partner success criteria are not included in this document.
 
-- Finish provisioning of all OCI resources
-- Establish all required network connectivity
-- Successfully pass all test cases
-- Finished handover with documentation
-- Complete the Implementation Security Checklist
+- Complete provisioning of all in-scope OCI resources.
+- Establish all required network connectivity.
+- Successfully pass all agreed test cases.
+- Complete handover with supporting documentation.
+- Complete the Implementation Security Checklist.
 
 ## Workplan
 
@@ -902,7 +912,7 @@ PPM   | None
 
 *Guide:*
 
-*Describe deliverables within the implementation scope. Including this documentation as Solution Definition and the later following Solution Design. This should be a generic reusable text, provided by the implementers.*
+*Describe deliverables within the implementation scope, including this Solution Definition and the later Solution Design. This should be reusable text provided by the implementers.*
 
 ### Included Activities
 <!--
@@ -915,7 +925,7 @@ PPM   | None
 
 *Guide:*
 
-*Describe the implementation activities in detail. It does not need to include a list of cloud services or OCI capabilities, but rather includes activities such as 'Provisioning of Infrastructure Components'. Include scope boundaries in terms of the number of environments, resource count to be provisioned, data volume to be migrated, etc.*
+*Describe implementation activities in detail. This section does not need to list every cloud service or OCI capability. Instead, describe activities such as 'Provisioning of Infrastructure Components'. Include scope boundaries such as number of environments, resources to be provisioned, and data volume to be migrated.*
 
 *Example:*
 The implementation scope of work includes the following activities:
@@ -927,13 +937,13 @@ The implementation scope of work includes the following activities:
   * DRG and inter-VCN routing
   * Deployment of standard Security lists and NSG in VCN
   * Deployment of Route Tables in VCNs
-- Configure one site-to-site IPSec VPN between OCI & on-premises
+- Configure one site-to-site IPSec VPN between OCI and on-premises.
 - Configure Web Application Firewall to route the incoming internet traffic to Load Balancers and configure recommended rules
 - Configure bastion service to allow admin users to connect to the tenancy through the internet access
 
 **Security**
 - Enable Cloud Guard
-- Enable Datasafe and Register the Databases in scope
+- Enable Data Safe and register the databases in scope
 - Enable VSS
 - Configure OCI IAM Domains
 
@@ -952,24 +962,24 @@ PPM   | None
 
 *Guide:*
 
-*All activities not stated in the [Included Activities](#included-activities) are out of scope, as described in the [Disclaimer](#disclaimer). We do not provide a list of excluded activities to not create expectations based on a grey area between included and excluded activities. Here we only recommend further activities that happen to not be included but are not a full list of excluded activities.*
+*All activities not stated in [Included Activities](#included-activities) are out of scope, as described in the [Disclaimer](#disclaimer). This section recommends additional activities that are not included in the implementation scope. It is not intended to be a complete list of excluded activities.*
 
 *Example:*
 
-All items not explicitly stated to be within the scope of the implementation project will be considered out of scope. Oracle recommends the use of professional services to implement extensions or customizations beyond the original scope, or to operate the solution with any of Oracle's certified partners. As a part of this engagement, the below activities are considered to be out of implementation scope.
+All items not explicitly stated as in scope for the implementation project are considered out of scope. Oracle recommends using professional services or Oracle certified partners to implement extensions, customizations, or ongoing operations beyond the original scope. As part of this engagement, the following activities are considered out of implementation scope.
 
-- Any activities at customer on-premises or existing data center e.g. patching & backups required for migration
-- Any integration with other products than in scope
-- Any backup and recovery strategy implementation including third-party backup tool implementation
-- Application upgrade of any Oracle or other vendor or open source software.
-- SSL certificate management and configuration
-- Any form of testing and validations, including but not limited to performance testing, load testing, HA testing, DR testing, and tuning of any component in the solution
-- Any vulnerability assessment and penetration testing including server hardening, audit certification implementation
-- Any functional testing is to be conducted by the customer and/or third party involved
-- Any third-party firewall implementation, security tools, monitoring tools implementation
-- Troubleshooting existing open issues, including the performance of the application
-- Training on deployed products and OCI services
-- Run and maintain the support of the environment and end-user training
+- Activities in the customer's on-premises or existing data center, such as patching and backups required for migration.
+- Integration with products not included in scope.
+- Backup and recovery strategy implementation, including third-party backup tooling.
+- Application upgrades for Oracle, third-party vendor, or open source software.
+- SSL certificate management and configuration.
+- Testing and validation, including performance testing, load testing, HA testing, DR testing, and tuning of any solution component.
+- Vulnerability assessment, penetration testing, server hardening, or audit certification implementation.
+- Functional testing conducted by the customer or an involved third party.
+- Third-party firewall, security tool, or monitoring tool implementation.
+- Troubleshooting existing open issues, including application performance issues.
+- Training on deployed products and OCI services.
+- Ongoing run, maintain, support, and end-user training activities.
 
 
 ### Timeline
@@ -992,26 +1002,26 @@ PPM   | C/I
 ### Implementation RACI
 *Guide:*
 
-*Describe for all activities the RACI (Responsible, Accountable, Consultant, Informed) matrix*
+*Describe the RACI matrix for all activities. RACI means Responsible, Accountable, Consulted, and Informed.*
 
 *Example:*
 
 Num      | Activity                                      | Oracle | Customer
 ---    | ------                                           | ---        | ---
 1  | Conduct Project Kickoff  | AR  |  C
-2  | Provide access to the source environment, including all the relevant ports opened   | I  |AR
+2  | Provide access to the source environment, including all required open ports   | I  |AR
 3  | Provide VPN credentials for Oracle team, OCI console access details |  I | AR
-4  | Prepare Source System, apply required patches on source environments for migration, and take source environment backup to OCI  | I  | AR
+4  | Prepare source systems, apply required patches on source environments for migration, and back up the source environment to OCI  | I  | AR
 5  | Backup of source Database   |  C | AR
-6  | Provision Landing Zone with  related Network and policies in scope  |  AR |  C
-7  | Configure site-to-site VPN between onPrem and OCI tenancy  | AR  | C
-8  | Migrate non-Prod database in scope  | AR  |  C
-9  | Perform Pre and Post functional migration tasks  | I   | AR
-10  | Perform functional/customization/integration testing and Validation of application within the project timeline  | I  |  AR
+6  | Provision the landing zone with related network resources and policies in scope  |  AR |  C
+7  | Configure site-to-site VPN between on-premises and the OCI tenancy  | AR  | C
+8  | Migrate the non-production database in scope  | AR  |  C
+9  | Perform pre-migration and post-migration functional tasks  | I   | AR
+10  | Perform functional, customization, integration testing, and application validation within the project timeline  | I  |  AR
 11  | Provide OCI technical support during validation  | AR  |  C
 12  | Prepare production runbook and perform Production Cutover  | C   | AR
-13  | Provide timely support for HW, OS, network related issues at source  | I  |  AR
-14  | Procure of SSL Certificates  | C  |  AR
+13  | Provide timely support for hardware, operating system, and network-related issues at source  | I  |  AR
+14  | Procure SSL certificates  | C  |  AR
 15  | Provide access to My Oracle Support required for product support along with CSI number  | I  |  AR
 
 **R- Responsible, A- Accountable, C- Consulted, I- Informed **
@@ -1028,27 +1038,27 @@ PPM   | None
 
 *Guide:*
 
-*List any assumptions, if any, which could impact the solution architecture or the implementation.*
+*List assumptions that could affect the solution architecture or implementation.*
 
 *Example:*
 
 **Generic assumptions**
 - It is assumed that all required contractual agreements between Oracle and the Customer are in place to ensure uninterrupted execution of the project.
-- It is assumed that all work will be done remotely and within either central European time or India Standard Time normal office working hours.
-- It is assumed that upgrades are excluded from the scope of work and no production systems/production cutover is part of the scope of work undertaken by the Oracle Service
-- It is assumed that all required Oracle cloud technical resources are available for use during the duration of the project and that engineers involved have been granted the appropriate access to those technical resources by the customer before the start of the project.
-- It is assumed that all required customer resources, and if applicable third-party resources, are available during the duration of the project to work openly and collaboratively to realize the project goals uninterruptedly.
-- It is assumed that all required customer resources, and if applicable third-party resources are aware of all technical and non-technical details of the as-is and to-be components. All resources are committed to technical work as far as is needed for the execution of the project.
-- It is assumed that all required documentation, system details, and access needed for the execution of the project can be given/granted to parties involved when and where deemed needed for the success of the project.
-- It is assumed that the customer will have adequate licenses for all the products that may/will be used during the project and that appropriate support contracts for those products are in place where the customer will take the responsibility of managing any potential service request towards a support organization to seek resolution of a problem.
-- It is assumed the customer will provide the appropriate level of information and guidance on rules and regulations which can directly and/or indirectly influence the project or the resulting deliverables. This includes, however not limited to, customer-specific naming conventions, security implementation requirements, internal SLA requirements as well as details for legal and regulatory compliance. It will be the responsibility of the customer to ensure that the solution will adhere to this.
-- It is assumed that under the customer's responsibility, the customer will ensure and validate that the solution will be placed under the proper controls for ensuring business continuity, system availability, recoverability, security control, and monitoring and management as part of a post-project task.
-- It is assumed that the customer will take responsibility for testing all functional and non-functional parts of the solution within the provided timeline and ensure a proper test report will be shared with the full team (including customer, Oracle, and if applicable third party).
-- It is assumed that any requirement, deliverable, or expectation that is not clearly defined as in-scope of the project will not be handled as part of the project and is placed under the responsibility of the customer to be handled outside of the project.
+- It is assumed that all work will be performed remotely during standard office hours in either Central European Time or India Standard Time.
+- It is assumed that upgrades are excluded from the scope of work and that production systems or production cutover activities are not part of the Oracle service scope.
+- It is assumed that all required Oracle Cloud technical resources are available during the project and that involved engineers have been granted appropriate access to those resources by the customer before the project starts.
+- It is assumed that all required customer resources, and any applicable third-party resources, are available during the project and will collaborate openly to achieve the project goals without interruption.
+- It is assumed that all required customer resources, and any applicable third-party resources, understand the technical and non-technical details of the as-is and to-be components. All resources are committed to the technical work required to execute the project.
+- It is assumed that all required documentation, system details, and access needed for project execution can be provided to the involved parties when required for project success.
+- It is assumed that the customer has adequate licenses for all products used during the project and that appropriate support contracts are in place. The customer is responsible for managing service requests with the relevant support organizations.
+- It is assumed that the customer will provide information and guidance on rules and regulations that can directly or indirectly influence the project or deliverables. This includes customer-specific naming conventions, security requirements, internal SLA requirements, and legal or regulatory compliance requirements. The customer is responsible for ensuring that the solution adheres to these requirements.
+- It is assumed that the customer will ensure and validate, as part of post-project activities, that the solution is placed under appropriate controls for business continuity, availability, recoverability, security, monitoring, and management.
+- It is assumed that the customer is responsible for testing all functional and non-functional parts of the solution within the agreed timeline and will share a test report with the full team, including Oracle and any applicable third party.
+- It is assumed that any requirement, deliverable, or expectation not clearly defined as in scope will not be handled as part of the project and remains the customer's responsibility outside the project.
 
 **Project-specific assumptions**
-- It is assumed that sufficient network bandwidth (greater than 200 GB) is available between OCI and Customer onPremise for any data transfer.
-- It is assumed that the customer, or a partner of your choice, will own the control, access, management, and further development of your OCI environment following the deployment of your solution.
+- It is assumed that sufficient network bandwidth is available between OCI and the customer's on-premises environment for the required data transfer.
+- It is assumed that the customer, or a partner chosen by the customer, will own control, access, management, and further development of the OCI environment after the solution is deployed.
 
 ### Obligations
 <!--
@@ -1061,15 +1071,15 @@ PPM   | None
 
 *Guide:*
 
-*List any obligations required by the customer to perform or have available, if any, which could impact the architecture or the implementation. Please always include this chapter to capture the obligation that we have admin access to the customer's tenancy.*
+*List customer obligations that could affect the architecture or implementation. Always include this chapter to capture the requirement for administrator access to the customer's tenancy.*
 
 *Example:*
 
 - You will have purchased the appropriate Universal Credits for the services required for the project.
 - The implementation team will have admin access to the customer's tenancy for implementation.
-- You will ensure the appropriate product training has been obtained to maintain and support the implementation
+- You will ensure that appropriate product training has been obtained to maintain and support the implementation.
 - Your business team will be available for the Testing phase, which will be completed within the agreed testing window.
 - You will provide project management for the project and will manage any third-party suppliers or vendors.
-- You will provide the implementation team with appropriate access to your tenancy & relevant on-premises applications/database to perform implementation activities. We recommend the least-privilege access principle.
-- You will revoke implementor access on production goLive or after project completion.
+- You will provide the implementation team with appropriate access to your tenancy and relevant on-premises applications or databases to perform implementation activities. We recommend using the least-privilege access principle.
+- You will revoke implementer access at production go-live or after project completion.
 - You will take consistent and restorable backups of your existing data and application before implementation.
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/discovery-questionnaire/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/discovery-questionnaire/README.md
index e0d67e96c..07f3dd6b2 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/discovery-questionnaire/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/discovery-questionnaire/README.md
@@ -2,7 +2,7 @@
 
 This document can be used as a reference questionnaire to collect the required details for a project involving Oracle Cloud VMware Solution.
 
-Reviewed: 12.11.2025
+Reviewed: 24.06.2026
 
 # When to use this asset?
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/README.md
index cb9659e03..2616402fe 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/README.md
@@ -8,7 +8,7 @@ Terraform can be used both to provision and manage an OCVS environment. In the f
 
 Examples created by: Richard Garsthagen, feedback is welcome! Please see the 'Issue' feature in GitHub.
 
-Reviewed: 12.11.2025
+Reviewed: 24.06.2026
 
 # License
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/addhost-multiad/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/addhost-multiad/README.md
index 75f55b5e2..8100ceb44 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/addhost-multiad/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/addhost-multiad/README.md
@@ -2,7 +2,7 @@
 
 Automate the provisioning and management of an OCVS environment.
 
-Reviewed: 12.11.2025
+Reviewed: 24.06.2026
 
 # When to use this asset?
 This is an example Terraform script to provision an OCVS SDDC in multi-ad architecture in a 3 AD region, based on DenseIO shape, using VSAN for storage.
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/multi-host-denseio-single-cluster-sddc/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/multi-host-denseio-single-cluster-sddc/README.md
index 7ae4c9621..3e75e7df8 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/multi-host-denseio-single-cluster-sddc/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/multi-host-denseio-single-cluster-sddc/README.md
@@ -2,7 +2,7 @@
 
 Automate the provisioning and management of an OCVS environment.
 
-Reviewed: 12.11.2025
+Reviewed: 24.06.2026
 
 # When to use this asset?
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/multi-host-standard-single-cluster-sddc/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/multi-host-standard-single-cluster-sddc/README.md
index 3c9fe0ebf..340271f96 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/multi-host-standard-single-cluster-sddc/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/multi-host-standard-single-cluster-sddc/README.md
@@ -2,7 +2,7 @@
 
 Automate the provisioning and management of an OCVS environment.
 
-Reviewed: 12.11.2025
+Reviewed: 24.06.2026
 
 # When to use this asset?
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/singlehost-sddc/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/singlehost-sddc/README.md
index 1036f71cd..1cc49cad0 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/singlehost-sddc/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/singlehost-sddc/README.md
@@ -2,7 +2,7 @@
 
 Automate the provisioning and management of an OCVS environment.
 
-Reviewed: 12.11.2025
+Reviewed: 24.06.2026
 
 # When to use this asset?
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/vlan/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/vlan/README.md
index 78b49adb2..1a77b9a6c 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/vlan/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/vlan/README.md
@@ -2,7 +2,7 @@
 
 Automate the provisioning and management of an OCVS environment.
 
-Reviewed: 12.11.2025
+Reviewed: 24.06.2026
 
 # When to use this asset?
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/vlan/files/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/vlan/files/README.md
index 34dace959..875f53d4c 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/vlan/files/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/ocvs-terrafom-automation/vlan/files/README.md
@@ -15,7 +15,7 @@ data oci_ocvp_esxi_hosts export_esxi_hosts{
 }
 ```
 
-Reviewed: 11.12.2023
+Reviewed: 24.06.2026
 
 ## New VLAN Assignment to your OCVS environment
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vcenter-to-oci-notifications/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vcenter-to-oci-notifications/README.md
index 880b815d1..448d786b3 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vcenter-to-oci-notifications/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vcenter-to-oci-notifications/README.md
@@ -2,7 +2,7 @@
 
 This script enables integration between vCenter alarms and the OCI Notifications service. By forwarding vCenter alarms to OCI Notifications, you can more easily manage who receives notifications and choose from multiple notification protocols (such as email, Slack, custom webhooks, or PagerDuty) supported by OCI. This simplifies recipient management and extends the reach of your alerts beyond the vCenter infrastructure.
 
-Reviewed: 26.11.2025
+Reviewed: 24.06.2026
 
 # When to use this asset?
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vcenter-to-oci-notifications/files/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vcenter-to-oci-notifications/files/README.md
index 5a73959a2..34563d4f0 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vcenter-to-oci-notifications/files/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vcenter-to-oci-notifications/files/README.md
@@ -69,7 +69,7 @@ If you have setup the Notification topic and for instance have an user subscribe
 
 Script created by: richard.garsthagen@oracle.com, feedback is welcome! Please see the 'Issue' feature in GitHub.
 
-Reviewed: 26.11.2025
+Reviewed: 24.06.2026
 
 # License
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-disaster-recovery-guides/vmware-live-site-recovery/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-disaster-recovery-guides/vmware-live-site-recovery/README.md
index 351adf452..5ad07d49c 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-disaster-recovery-guides/vmware-live-site-recovery/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-disaster-recovery-guides/vmware-live-site-recovery/README.md
@@ -2,7 +2,7 @@
 
 This repository contains a detailed guide for using VLSR 9.x with Oracle Cloud VMware Solution.
 
-Reviewed: 17.11.2025
+Reviewed: 24.06.2026
 
 # When to use this asset?
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-disaster-recovery-guides/vsphere-replication/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-disaster-recovery-guides/vsphere-replication/README.md
index 3b32b7782..e99aeb9e3 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-disaster-recovery-guides/vsphere-replication/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-disaster-recovery-guides/vsphere-replication/README.md
@@ -2,7 +2,7 @@
 
 This repository contains a detailed guide for using vSphere Replication 9.x with Oracle Cloud VMware Solution.
 
-Reviewed: 17.11.2025
+Reviewed: 24.06.2026
 
 # When to use this asset?
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/README.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/README.md
index 46488d312..60f1c7646 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/README.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/README.md
@@ -2,7 +2,7 @@
 
 This repository contains an in-depth guide for the migration of VMware workloads to Oracle Cloud VMware Solution. It offers a high-level solution definition of the deployment architecture and migration process of workloads from a current VMware environment to Oracle Cloud VMware Solution. The document is aimed at capturing the current state architecture with requirements and provides a prospective state, potential project scope, and anticipated timelines for the migration. 
 
-Reviewed: 12.11.2025
+Reviewed: 24.06.2026
 
 # When to use this asset?
 
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/files/OCVS-Migration-Solution-Definition-Template.md b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/files/OCVS-Migration-Solution-Definition-Template.md
index f7798b1be..b195f0388 100644
--- a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/files/OCVS-Migration-Solution-Definition-Template.md
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/files/OCVS-Migration-Solution-Definition-Template.md
@@ -22,7 +22,7 @@
 | VCN   | Virtual Cloud Network                 |
 | DRG   | Dynamic Routing Gateway               |
 | CPE   | Customer Premises Equipment           |
-| FC    | OCI Fast Connect Connection           |
+| FC    | OCI FastConnect Connection            |
 | IPSec | OCI IPSec VPN Connection              |
 | SL    | Security List                         |
 | NSG   | Network Security Group                |
@@ -43,11 +43,11 @@
 
 ## Document Purpose
 
-This document provides a high-level solution definition for the Oracle solution and aims at describing the current state, and to-be state as well as a potential high-level project scope and timeline for Lift.
+This document provides a high-level solution definition for the Oracle solution. It describes the current state, the target state, and a potential high-level project scope and timeline for Oracle Cloud Lift.
 
 The document may refer to a ‘Workload’, which summarizes the full technical solution for a customer (You) during a single engagement. The Workload is described in the chapter [Workload Requirements and Architecture](#workload-requirements-and-architecture).
 
-This is a living document, additional sections will be added as the engagement progresses resulting in a final Document to be handed over to the Lift.
+This is a living document. Additional sections will be added as the engagement progresses, resulting in a final document to be handed over at the end of the Lift engagement.
 
 # Business Context
 
@@ -55,7 +55,7 @@ This is a living document, additional sections will be added as the engagement p
 
 A Company Making Everything is located in Frankfurt, Germany, and is the largest consumer electronics company. A Company Making Everything has 2500 employees at this location, generating millions of dollars in sales. There are subsidiaries under A Company Making Everything corporate family which contribute to overall sales for the parent organization.
 
-A Company Making Everything is an existing Oracle Cloud customer and currently consuming various OCI services such as network, compute, storage, and databases in OCI Frankfurt Region. The current Production, Test, Dev & DMZ environments are hosted in an on-premises infrastructure with physical and VMware servers. The customer has a cloud and digital transformation strategy and would like to exit the data center by moving the on-premises workloads to the cloud.
+A Company Making Everything is an existing Oracle Cloud customer and currently consumes various OCI services, such as networking, compute, storage, and databases, in the OCI Frankfurt region. The current production, test, development, and DMZ environments are hosted in on-premises infrastructure with physical and VMware servers. The customer has a cloud and digital transformation strategy and would like to exit the data center by moving on-premises workloads to the cloud.
 
 The mission-critical application workloads are hosted primarily in VMware. The customer is looking for quick and seamless migration to the cloud with minimal interruption to the services. They have decided to use the Oracle Cloud VMware Solution for quick migration of the VMware workloads before their current data center contract expires. The Oracle Cloud VMware Solution offers flexible, highly scalable, and cost-effective solutions to host A Company Making Everything’s critical workloads without disrupting their core business.
 
@@ -67,36 +67,36 @@ The mission-critical application workloads are hosted primarily in VMware. The c
 
 A Company Making Everything is running a strategic program in FY23 called EXAMPLE. As part of their initiative, one pillar is dedicated to their IT cost saving. A Company Making Everything is planning to reduce their IT estate spending by 15% in the current FY. Oracle can help A Company Making Everything by reducing the VMware deployment complexity and operations while optimizing IT costs. A Company Making Everything IT department wants to innovate other LoBs and enable quick-time-to-market for various applications and business needs. This allows A Company Making Everything to stay ahead in a competitive market.
 
-The Oracle Cloud VMware Solution is a customer-managed Software-defined Data Center solution offering customers a choice to run flexible infrastructure to host mission-critical workloads. The customer can seamlessly move their workloads from the on-premises VMware environment to Oracle Cloud VMware Solution promptly with the help of the native migration tool offered with the solution. Since the platform remains the same for migrated workloads there are no efforts required to re-factoring the application rather customer can focus on the digital transformation journey.
+Oracle Cloud VMware Solution is a customer-managed software-defined data center (SDDC) service that provides flexible infrastructure for mission-critical VMware workloads. Customers can move workloads from an on-premises VMware environment to Oracle Cloud VMware Solution by using VMware migration tooling such as HCX, subject to licensing, entitlement, compatibility, and lifecycle considerations. Because the VMware platform remains consistent, customers can reduce or avoid application refactoring and focus on their broader digital transformation journey.
 
 # Workload Requirements and Architecture
 
 ## Overview
 
-Oracle guides in planning, architecting, prototyping, and managing cloud migrations. Customers can move critical workloads in weeks, or even days, instead of months by leveraging these included services for customers.
+Oracle provides guidance for planning, architecting, prototyping, and managing cloud migrations. Customers can move critical workloads in weeks, or even days, instead of months by using these services.
 
-Oracle will support A Company Making Everything in setting up the target OCVS architecture based on customer business and technical requirements. Oracle will move selected VMs of the on-premise VMware workload to Oracle Cloud Infrastructure in the INSERT REGION region.
+Oracle will support A Company Making Everything in designing the target Oracle Cloud VMware Solution architecture based on customer business and technical requirements. Oracle will help move selected virtual machines from the on-premises VMware workload to Oracle Cloud Infrastructure in the INSERT REGION region.
 
 **Thus, the objectives of this document are to:**
 
-1.  Review together the existing on-premise architecture, map it to relevant Oracle OCI services, and propose a high-level tailored cloud architecture design.
+1.  Review the existing on-premises architecture, map it to relevant Oracle Cloud Infrastructure services, and propose a tailored high-level cloud architecture.
 2.  Define the Oracle Cloud Lift Services scope to help A Company Making Everything to physically migrate the agreed workload to the target cloud platform.
 
 **The goals of this document are to:**
 
-Additionally, the [Document Purpose]{#document-purpose} these are the high-level goals for this document:
+The high-level goals for this document are:
 
-1.  Provide the architecture guidelines as per A Company Making Everything needs for the target cloud OCI architecture.
-2.  Fitting the solution into A Company Making Everything the OCI ecosystem.
-3.  Address all OCVS-related aspects at security, network, compute, storage, and other levels for implementing the target cloud architecture.
-4.  Set up the OCVS cloud environment according to the agreed design & architecture.
-5.  Define the scope of the potential LIFT services migration of the A Company Making Everything workload.
+1.  Provide architecture guidance aligned with A Company Making Everything's needs for the target OCI architecture.
+2.  Fit the solution into the A Company Making Everything OCI ecosystem.
+3.  Address Oracle Cloud VMware Solution design considerations across security, networking, compute, storage, operations, and related areas.
+4.  Define the Oracle Cloud VMware Solution environment according to the agreed design and architecture.
+5.  Define the potential Oracle Cloud Lift migration scope for the A Company Making Everything workload.
 
 ## Non-Functional Requirements
 
 ### Regulations and Compliance
 
-At the time of this document creation, no Regulatory and Compliance requirements have been specified.
+At the time this document was created, no regulatory or compliance requirements were specified.
 
 ### Environments
 
@@ -107,11 +107,11 @@ At the time of this document creation, no Regulatory and Compliance requirements
 
 ### High Availability and Disaster Recovery Requirements
 
-At the time of this document creation, no high availability and disaster recovery requirements have been specified.
+At the time this document was created, no high availability or disaster recovery requirements were specified.
 
 ### Security Requirements
 
-At the time of this document creation, no security requirements have been specified.
+At the time this document was created, no security requirements were specified.
 
 ## Current State Architecture
 
@@ -119,7 +119,7 @@ The current state architecture covers the current on-premises workloads.
 
 ### Current State IT Architecture (VMware)
 
-A Company Making Everything current environment is running in a data center (DC LOCATION) based on hardware (HARDWARE MODELS) infrastructure and VMware vSphere Hypervisor (ESXi).
+A Company Making Everything's current environment runs in a data center (DC LOCATION) on hardware (HARDWARE MODELS) infrastructure and VMware vSphere Hypervisor (ESXi).
 
 **The Current VMware footprint consists of:**
 
@@ -268,23 +268,23 @@ A Company Making Everything is responsible for implementing, managing, and maint
 
 ### OCI Secure Landing Zone Architecture (OCVS)
 
-All the above OCI and OCVS networking and security services and principles are implemented through the concept of a Landing Zone. The following diagram illustrates the Landing Zone reference architecture specific to the deployment of OCVS.
+The Oracle Cloud Infrastructure and Oracle Cloud VMware Solution networking and security services described above are implemented through a landing zone. The following diagram illustrates the landing zone reference architecture for Oracle Cloud VMware Solution.
 
-![OCVS landing zone](images/landing_zone.png)
+![OCVS landing zone](images/Landing_zone.png)
 
-This architecture is designed specifically for Oracle Cloud VMware Solution which sits on top of the OCI core services such as Bare Metal Compute, and VCN networking. The architecture starts with the compartment design for the tenancy along with groups and policies for the segregation of duties.
+This architecture is designed specifically for Oracle Cloud VMware Solution, which runs on Oracle Cloud Infrastructure core services such as Bare Metal Compute and Virtual Cloud Network resources. The architecture starts with tenancy compartment design, groups, and policies to support segregation of duties.
 
-In Landing Zone, tenancy should have a dedicated compartment for VMware SDDC deployment. The existing tenancy can also be used but it is recommended to segregate the VMware SDDC environment from other OCI resources. The VMware SDDC Compartment is assigned a group with appropriate permissions for managing resources in the compartment and for accessing required resources in other compartments. As a best practice, it is recommended to create a dedicated compartment for VCN leveraged by the OCVS deployment to keep the networking resources completely separated in a dedicated compartment.
+In the landing zone, the tenancy should have a dedicated compartment for the VMware SDDC deployment. An existing tenancy can be used, but the VMware SDDC environment should be separated from other Oracle Cloud Infrastructure resources. The VMware SDDC compartment is assigned to a group with the permissions required to manage resources in that compartment and access required resources in other compartments. As a best practice, create a dedicated compartment for the VCN used by Oracle Cloud VMware Solution so networking resources are isolated in their own compartment.
 
-The VMware SDDC compartment will be utilized to deploy the SDDC service. The SDDC network compartment will host dedicated VCN resources to maintain the isolation of the VMware and network resources and thus use the IAM policies for network resource and access management. Oracle Cloud VMware Solution deployment workflow is a fully automated process and takes care of provisioning of required to compute & networking resources maintaining the security standard.
+The VMware SDDC compartment is used to deploy the SDDC service. The SDDC network compartment hosts the dedicated VCN resources required to isolate VMware and network resources, and IAM policies control network resource access and management. The Oracle Cloud VMware Solution deployment workflow is automated and provisions the required compute and networking resources while maintaining the expected security posture.
 
-The Landing Zone for OCVS includes pre-configured networking resources such as subnet, VLANs, Network Security Group, Security List, and Route Tables maintaining the security posture needed for enterprise VMware workloads. Also, it includes pre-configured Compute Bare Metal services required for VMware hypervisor operation. Additionally, VMware NSX as a Software Defined Networking is pre-configured but isolated in an overlay network zone.
+The Oracle Cloud VMware Solution landing zone includes preconfigured networking resources such as subnets, VLANs, network security groups, security lists, and route tables to support the security posture required for enterprise VMware workloads. It also includes the Bare Metal Compute resources required for VMware hypervisor operation. VMware NSX is configured as the software-defined networking layer and is isolated in an overlay network zone.
 
-Additional OCI services such as Cloud Guard, Events, Notifications, and WAF can be used to operate and monitor OCI resources for Oracle Cloud VMware Solutions such as OCI Compute, and OCI Network. The Notifications are set using Topics and Events for alerting administrators about changes in the deployed resources for this environment.
+Additional Oracle Cloud Infrastructure services such as Cloud Guard, Events, Notifications, and Web Application Firewall can be used to operate and monitor Oracle Cloud VMware Solution resources, including OCI Compute and OCI Networking resources. Notifications can be configured with topics and events to alert administrators about changes in deployed resources.
 
-**Please Note** The VMware workloads can use limited OCI services when it comes to integration of VMware SDDC workloads to OCI. Low-level design of Landing zone with A Company Making Everything" relevant specific technical details will be provided during the architecture Design discovery process. The network for the SDDC network should not overlap with the existing networks in A Company Making Everything" tenancy. The SDDC can be scaled up to a maximum of 64 hosts with /21 SDDC CIDR range.
+**Please note:** VMware workloads can integrate with selected Oracle Cloud Infrastructure services, subject to the design and connectivity model used for the VMware SDDC. The low-level landing zone design, including technical details specific to A Company Making Everything, will be provided during the architecture design discovery process. The SDDC network must not overlap with existing networks in the A Company Making Everything tenancy. With a /21 SDDC CIDR range, the SDDC can scale up to a maximum of 64 hosts.
 
-**Note:** The table is a representation of the sample network layout for the /22 network however based on the SDDC CIDR range selected we can expect an automated network layout created by the SDDC provisioning operation with different network range for VLANS. SDDC workload CIDR will be identified as a part of the low-level design during the implementation.
+**Note:** The following table shows a sample network layout for a /22 network. The actual VLAN network ranges are created automatically by the SDDC provisioning workflow and depend on the selected SDDC CIDR range. The SDDC workload CIDR will be identified as part of the low-level design during implementation.
 
 | VLAN Name                   | CIDR Range    |
 |:----------------------------|:--------------|
@@ -302,40 +302,43 @@ Additional OCI services such as Cloud Guard, Events, Notifications, and WAF can
 
 ### Physical Architecture
 
-The future state architecture covers the current on-premises workloads to be hosted on Oracle Cloud VMware Solution(OCVS). The OCVS is deployed at the Availability Domain (AD) in the OCI region and spans across 3 Fault Domains (FD) in the region. The OCI Bare Metal (BM) instances utilized by the service are spread across the Fault Domain (FD) in a round-robin fashion offering complete redundancy to the OCVS workloads. The OCVS comes with two distinct architectures as represented below.
+The future state architecture covers the current on-premises workloads that will be hosted on Oracle Cloud VMware Solution. Oracle Cloud VMware Solution is deployed in an availability domain within the selected Oracle Cloud Infrastructure region and spans three fault domains in that region. The OCI Bare Metal instances used by the service are distributed across fault domains in a round-robin pattern to provide redundancy for Oracle Cloud VMware Solution workloads. Oracle Cloud VMware Solution supports two primary architecture options:
 
--   OCVS with DenseIO server - This architecture primarily uses vSAN Storage leveraging NVMe drives from the local Bare Metal (BM) servers.
--   OCVS with Standard Shapes - This architecture is completely based on the OCI Block Storage as a primary storage option for the VM workloads.
+-   Oracle Cloud VMware Solution with DenseIO shapes: This architecture primarily uses VMware vSAN storage backed by NVMe drives from the local Bare Metal servers.
+-   Oracle Cloud VMware Solution with Standard Shapes: This architecture uses OCI Block Storage as the primary storage option for virtual machine workloads.
+
+Bring Your Own License (BYOL) for Oracle Cloud VMware Solution is generally available and aligns Oracle Cloud VMware Solution with Broadcom's VMware Cloud Foundation (VCF) license portability model. Oracle discontinued new long-term license-included Oracle Cloud VMware Solution SKUs, including monthly, 1-year, and 3-year license-included options, effective March 22, 2026. New SDDCs could be deployed using the license-included model until March 21, 2026, and existing SDDCs could continue scaling out with hourly license-included hosts until May 20, 2026. After these dates, all new Oracle Cloud VMware Solution capacity must be provisioned using BYOL. Customers must bring, procure, register, allocate, and maintain the VMware licenses required for the selected SDDC architecture, including any migration, disaster recovery, backup, or operations tooling. Eligible VMware VCF subscription entitlements are registered in Oracle Cloud VMware Solution License Management, allocated to the target OCI region, and selected during SDDC provisioning, workload cluster creation, or ESXi host scale-out.
 
 ![Future State Architecture](images/ocvs-overview.png)
 
-Oracle Cloud VMware Solution is the central part of this deployment and provides a fully automated implementation of a VMware software-defined data center (SDDC) within your Oracle Cloud Infrastructure tenancy. The solution runs on Oracle Cloud Infrastructure Bare Metal Compute and contains the following VMware components:
+Oracle Cloud VMware Solution is the central component of this deployment. It provides an automated implementation of a VMware software-defined data center (SDDC) within the customer's Oracle Cloud Infrastructure tenancy. The solution runs on Oracle Cloud Infrastructure Bare Metal Compute and includes the following VMware components, subject to customer licensing and entitlement:
 
 -   VMware vSphere Hypervisor (ESXi)
 -   VMware vCenter Server
 -   VMware vSAN
 -   OCI Block Storage
 -   VMware NSX-T
--   VMware HCX Advanced
+-   VMware HCX
 
-High-level OCVS-based cloud architecture for A Company Making Everything target cloud deployment is outlined in the picture below.
+The high-level Oracle Cloud VMware Solution-based cloud architecture for the A Company Making Everything target cloud deployment is shown below.
 
 ![High Level OCVS architecture](images/futurestatearchitecturemigration.png)
 
-The architecture has the following components:
+The architecture includes the following components:
 
 **OCVS**
 
-The **VMware SDDC** comes in with vSphere 7.0 version. The OCVS SDDC consists of vSphere (ESXi + vCenter), NSX-T, vSAN & HCX. The SDDC deployment can be on OCI DenseIO shapes that offer vSAN Storage or it can be on OCI Standard Shape with OCI Block Storage as a primary storage option.
+The **VMware SDDC** consists of vSphere (ESXi and vCenter), NSX-T, vSAN, and HCX. The SDDC can be deployed on OCI DenseIO shapes that provide vSAN storage, or on OCI Standard Shapes with OCI Block Storage as the primary storage option. The solution design must confirm the VMware Cloud Foundation, vSphere, vSAN, NSX, HCX, VMware Live Recovery, Site Recovery Manager, or other VMware entitlements required for the selected architecture and migration approach.
 
--   **VMware HCX** - Application mobility platform designed for simplifying application migration, workload re-balancing, and business continuity across data centers and clouds. This will allow the seamless migration of VMware workloads to OCVS.
--   **HCX Manager** – HCX manager is an appliance deployed in Oracle Cloud VMware Solution. HCX manager will be paired with an on-premises vCenter through HCX Connector.\
--   **HCX Connector** – HCX connector is an appliance deployed at an on-premises vCenter server which will be then paired with the HCX manager in the cloud for the base configuration necessary for workload migration.\
--   **VMware NSX-T** - This is NSX-T Data Center implementation as part of the SDDC stack used for Software Defined Networking. The migrated workloads can use NSX network segments for networking usage. NSX-T offers full perimeter services configuration in OCVS environments such as Load Balancer, Routing, Switching, firewall, and micro-segmentation.
--   **VMware vSAN** - VMware vSAN is a software-defined storage solution offered as part of the OCVS SDDC solution. The vSAN has been configured by leveraging locally attached NVMe all-flash disks from each OCI Bare Metal server to offer common storage for workloads.
--   **OCI Block Storage** - The OCI Block storage can be leveraged as an additional storage option with DenseIO compute SDDC along with vSAN. The Standard Shape OCVS environment consists of OCI block storage as the only primary storage option.
--   **VMware vSphere** - Includes ESXi and vCenter servers
--   **FastConnect** - OCI FastConnect is a dedicated private high-speed network link connected to A Company Making Everything Data Center and OCI region. The FastConnect will be leveraged for migrating the workloads over the network.
+-   **VMware licensing** - New Oracle Cloud VMware Solution capacity is consumed with customer-provided VMware licenses under the BYOL model. The required VCF license allocations must be registered in Oracle Cloud VMware Solution License Management and available in the target OCI region before provisioning or scale-out.
+-   **VMware HCX** - An application mobility platform designed to simplify application migration and workload rebalancing across data centers and clouds. HCX can support selected mobility use cases for VMware workloads to Oracle Cloud VMware Solution, subject to licensing, entitlement, compatibility, and lifecycle considerations.
+-   **HCX Manager** - An appliance deployed in Oracle Cloud VMware Solution. HCX Manager is paired with the on-premises vCenter through HCX Connector.
+-   **HCX Connector** - An appliance deployed with the on-premises vCenter Server and paired with HCX Manager in the cloud to provide the base configuration required for workload migration.
+-   **VMware NSX-T** - The NSX-T Data Center implementation that provides software-defined networking for the SDDC stack. Migrated workloads can use NSX network segments. NSX-T provides networking and security services for Oracle Cloud VMware Solution environments, including load balancing, routing, switching, firewalling, and micro-segmentation.
+-   **VMware vSAN** - A software-defined storage solution included with the Oracle Cloud VMware Solution SDDC. vSAN uses locally attached NVMe all-flash disks from each OCI Bare Metal server to provide shared storage for workloads.
+-   **OCI Block Storage** - OCI Block Storage can be used as additional storage with a DenseIO SDDC alongside vSAN. In a Standard Shape Oracle Cloud VMware Solution environment, OCI Block Storage is the primary storage option.
+-   **VMware vSphere** - Includes ESXi hosts and vCenter Server.
+-   **FastConnect** - Oracle Cloud Infrastructure FastConnect is a dedicated, private, high-speed network connection between the A Company Making Everything data center and the selected Oracle Cloud Infrastructure region. FastConnect can be used to migrate workloads over the network.
 
 ## Solution Considerations
 
@@ -343,55 +346,55 @@ The **VMware SDDC** comes in with vSphere 7.0 version. The OCVS SDDC consists of
 
 #### OCVS Resilience and Recovery
 
-Oracle Cloud VMware Solution is deployed at Availability Domain (AD) within the OCI region. Each Availability domain consists of Fault Domains to maintain a fault-tolerant and highly resilient environment. For more details about OCI Availability domains and Fault Domains refer to the [OCI documentation](https://docs.oracle.com/en-us/iaas/Content/General/Concepts/regions.htm).
+Oracle Cloud VMware Solution is deployed in an availability domain within the selected OCI region. Each availability domain contains fault domains that support fault-tolerant and resilient designs. For more information about OCI availability domains and fault domains, see the [OCI documentation](https://docs.oracle.com/en-us/iaas/Content/General/Concepts/regions.htm).
 
-The details of the Oracle Cloud Infrastructure SLAs are found in the link below. [OCI Service SLA](https://www.oracle.com/ae/cloud/sla/).
+Details of the Oracle Cloud Infrastructure SLAs are available at [OCI Service SLA](https://www.oracle.com/ae/cloud/sla/).
 
 ##### OCVS High Availability
 
-This section describes the VMware SDDC High Availability.
+This section describes VMware SDDC high availability.
 
-**OCI BM Compute (ESXi):** The OCI native services such as compute bare metal and VCN resources are highly resilient cloud service offerings from Oracle Cloud Infrastructure. OCI BM failure can be addressed by replacing the faulty node with a new ESXi host in the cluster.
+**OCI Bare Metal Compute (ESXi):** OCI native services such as Bare Metal Compute and VCN resources are resilient cloud services. An OCI Bare Metal host failure can be addressed by replacing the faulty node with a new ESXi host in the cluster.
 
-**OCI BM NVMe (vSAN):** The OCVS SDDC consist of vSAN for the software-defined storage layer. With vSAN's failure to tolerate (FTT) feature, host failures, and data loss can be effectively managed. Customers can utilize the vSAN SPBM (Storage Policy Based Management) which includes different RAID levels to protect the data.
+**OCI Bare Metal NVMe (vSAN):** The Oracle Cloud VMware Solution SDDC uses vSAN for the software-defined storage layer. vSAN failure to tolerate (FTT) policies help manage host failures and reduce the risk of data loss. Customers can use vSAN Storage Policy Based Management, including different RAID levels, to protect data.
 
-**OCVS Networking (NSX-T):** The OCVS SDDC consists of NSX-T implementation to manage software-defined networking. The NSX Edge, Managers/Controllers are deployed in a fully redundant manner to maintain high availability.
+**OCVS Networking (NSX-T):** The Oracle Cloud VMware Solution SDDC uses NSX-T to manage software-defined networking. NSX Edge nodes and NSX Managers are deployed redundantly to maintain high availability.
 
-**OCI Block Storage:** The OCI Block Storage offers the highest level of data resiliency by the backend system at the availability domain. The OCI Block storage being the primary storage option with OCVS does not require RAID configuration but rather relies on the resiliency offered by the Oracle Cloud Infrastructure.
+**OCI Block Storage:** OCI Block Storage provides backend data resiliency within the availability domain. When OCI Block Storage is used as the primary storage option with Oracle Cloud VMware Solution, RAID configuration is not required at the VMware layer; the design relies on the resiliency provided by Oracle Cloud Infrastructure.
 
 #### OCVS Backup
 
-This section describes a proposed backup architecture for A Company Making Everything workloads post-migration to OCVS. We recommend using the VEEAM backup and replication suite which works best with the VMware platform. However, other backup solutions such as Commvault can also be used.
+This section describes a proposed backup architecture for A Company Making Everything workloads after migration to Oracle Cloud VMware Solution. Veeam Backup & Replication is shown as an example because it is commonly used with VMware environments. Other backup solutions, such as Commvault, can also be used where they meet the customer's recovery, retention, licensing, and support requirements.
 
-The following diagram illustrates the proposed VEEAM backup architecture for A Company Making Everything"" application backup and restores requirement.
+The following diagram illustrates the proposed Veeam backup architecture for the A Company Making Everything application backup and restore requirements.
 
 ![OCVS backup](images/veeam.png)
 
 ##### Architecture Components Overview
 
-The VEEAM backup and restore integrates with the VMware vCenter server and offers backup and restore capabilities to the VMs deployed in SDDC as well as the instances deployed in OCI. Below summarizes the backup components as part of the architecture and a detailed description of each.
+Veeam Backup & Replication integrates with VMware vCenter Server and provides backup and restore capabilities for virtual machines deployed in the SDDC, as well as selected instances deployed in OCI. The following list summarizes the backup components in the architecture.
 
--   **VEEAM Backup Server** – VEEAM backup server is a software suite installed on the MS Windows operating system. It is recommended to deploy VEEAM outside of the SDDC Cluster. The VEEAM backup server will be installed on OCI Compute instance with MS Windows 2016 and above Operating System.
+-   **Veeam Backup Server** - Veeam Backup Server is a software suite installed on a Microsoft Windows operating system. It is recommended to deploy Veeam outside the SDDC cluster. The Veeam Backup Server will be installed on an OCI Compute instance running Microsoft Windows Server 2016 or later.
 
--   **MS SQL Cluster** – The Microsoft SQL cluster is required for VEEAM Backup Server Database. The SQL Nodes will be deployed in the same management subnet as that of the VEEAM backup Server and will use OCI native compute instances. The MS SQL will be deployed in High Availability mode using native AlwaysON clustering functionality. This will offer a fully redundant database for VEEAM. The SQL nodes will be spread across Fault Domains.
+-   **MS SQL Cluster** - The Microsoft SQL cluster is required for the Veeam Backup Server database. The SQL nodes will be deployed in the same management subnet as the Veeam Backup Server and will use OCI native compute instances. Microsoft SQL Server will be deployed in high availability mode using Always On availability groups. This provides a redundant database layer for Veeam. The SQL nodes will be spread across fault domains.
 
-**Note:** Depending upon the licensing requirement, we can use an MS SQL marketplace image where the license will be included. This needs to be discussed with the customer during the actual implementation.
+**Note:** Depending on licensing requirements, an Oracle Cloud Marketplace image for Microsoft SQL Server can be used where appropriate. This must be discussed with the customer during implementation.
 
--   **VEEAM Proxy** – VEEAM proxy is one of the main components of VEEAM Backup and replication. VEEAM proxy sits between the data source and target and is used to process jobs and deliver backup traffic. It allows to offload of the VEEAM Backup Server and has better performance resulting shorter backup window. There is a default proxy server that can be used if no proxy is deployed but it is recommended to deploy a VEEAM proxy for better backup performance. The proxy can be a Windows or Linux VM inside the OCVS SDDC.
+-   **Veeam Proxy** - The Veeam proxy is a core component of Veeam Backup & Replication. It sits between the data source and target, processes backup jobs, and moves backup traffic. It offloads work from the Veeam Backup Server and can improve performance, resulting in shorter backup windows. A default proxy can be used if no dedicated proxy is deployed, but a dedicated Veeam proxy is recommended for better backup performance. The proxy can be a Windows or Linux virtual machine inside the Oracle Cloud VMware Solution SDDC.
 
--   **Backup Repositories** – A backup repository is a storage location where VEEAM keeps backup files, VM copies, and metadata for replicated VMs. To configure a backup repository, you can use the following storage types:
+-   **Backup Repositories** - A backup repository is a storage location where Veeam stores backup files, virtual machine copies, and metadata for replicated virtual machines. The following storage types can be used:
 
-1.  **Direct Attached Storage (DAS):** You can add virtual and physical servers as backup repositories. The compute Microsoft Windows 2016 and above Instance in OCI with a bunch of block storage can be used as a Direct attached storage. This will be considered as a performance tier and recommended to use for better backup and restore performance. The VM with vSAN local storage disks can also be used as DAS but is not recommended to avoid a single point of failure.
+1.  **Direct Attached Storage (DAS):** Virtual and physical servers can be added as backup repositories. An OCI Compute instance running Microsoft Windows Server 2016 or later with attached OCI Block Volumes can be used as direct attached storage. This is considered a performance tier and is recommended for better backup and restore performance. A virtual machine with vSAN local storage disks can also be used as DAS, but this is not recommended because it can introduce a single point of failure.
 
 2.  **Network Attached Storage (Optional):** OCI File storage service NFS v3 service can be used as a Network Attached Storage.
 
-3.  **Object Storage:** You can use cloud storage services as backup repositories. The OCI Object storage is S3 compatible and can be used as a “Scale-out Repository” for the capacity tier or a direct backup repository. The Object storage scale-out repository can be configured to have an immediate copy of the backup, or it can be copied over after a specific schedule. It is recommended to use the OCI Block Storage attached to an instance as a primary storage option for backing up the VMs for better performance and backup operations. Object storage should only be considered as a capacity tier for long-term retention and archival purpose.
+3.  **Object Storage:** Cloud storage services can be used as backup repositories. OCI Object Storage is S3 compatible and can be used as a scale-out repository capacity tier or as a direct backup repository. The Object Storage scale-out repository can be configured to keep an immediate copy of the backup or copy data on a defined schedule. OCI Block Storage attached to a compute instance is recommended as the primary storage option for virtual machine backups when higher backup and restore performance is required. Object Storage should be considered for capacity tier, long-term retention, and archival use cases.
 
 **Important Notes:**
 
--   Sizing requirements & Design considerations should be followed from VEEAM official documentation.
--   A Company Making Everything will bring their own license for VEEAM. A Company Making Everything can discuss different VEEAM license options available with VEEAM directly and choose according to the requirement.\
--   A Company Making Everything can choose their choice of backup tool and Oracle will assist in architecting the necessary backup solution.
+-   Sizing requirements and design considerations should follow official Veeam documentation.
+-   A Company Making Everything will bring its own Veeam license. A Company Making Everything can discuss available Veeam license options directly with Veeam and choose the option that meets its requirements.
+-   A Company Making Everything can choose its preferred backup tool, and Oracle can assist in architecting the required backup solution.
 
 ### Security
 
@@ -422,57 +425,57 @@ The shared responsibility extends across different domains including identity ma
 
 The section below describes the security posture of Oracle Cloud VMware Solution and Oracle Cloud Infrastructure.
 
--   Access to the Customer's OCI tenancy is restricted and controlled using IAM and IDCS federations. Network sources can be optionally used to restrict access from known IP addresses within VCN or on-premises.
+-   Access to the customer's OCI tenancy is restricted and controlled using IAM and identity federation. Network sources can optionally restrict access to known IP addresses from a VCN or on-premises network.
 
--   Security in a subnet can be controlled by Security Lists and/or Network Security Groups. OCI is a zero-trust environment by default, you must explicitly permit traffic for known communication patterns. Additional security can be offered to Customer's external facing applications using OCI Web Application Firewall.
+-   Subnet security can be controlled by security lists and network security groups. OCI follows a zero-trust model by default, so traffic must be explicitly allowed for known communication patterns. OCI Web Application Firewall can provide additional protection for customer-facing applications.
 
--   VLAN resides in VCN and is only provisioned for OCVS service. Each VLAN is attached to the Network Security Group to control traffic. All traffic inside a VLAN is blocked by default.
+-   VLANs reside in the VCN and are provisioned for the Oracle Cloud VMware Solution service. Each VLAN is attached to a network security group to control traffic. Traffic within a VLAN is blocked by default until required rules are configured.
 
--   An NSX Segment is an overlay network that runs on top of the VMware virtualization stack. This network is independent outside of the VCN network. Any communication from the NSX overlay segment to OCI resources needs to be explicitly allowed through uplink interfaces using routing and controlled using security lists.
+-   An NSX segment is an overlay network that runs on top of the VMware virtualization stack. This network is independent of the VCN network. Communication from an NSX overlay segment to OCI resources must be explicitly allowed through uplink interfaces, routing, and security rules.
 
--   Security in an NSX Segment is managed by the NSX-T control plane, by default all traffic inside a segment is allowed. The NSX Micro-Segmentation enables you to increase the agility and efficiency of your network infrastructure while maintaining the highest level of security posture.
+-   Security within an NSX segment is managed by the NSX-T control plane. By default, traffic inside a segment is allowed. NSX micro-segmentation can improve network agility and operational efficiency while maintaining a strong security posture.
 
--   Users from an on-premises environment can securely connect to Oracle Cloud VMware Solution resources through IPSec and or FastConnect (for more details see Chapter 6.3 OCI networking).
+-   Users from an on-premises environment can securely connect to Oracle Cloud VMware Solution resources through IPSec VPN or FastConnect.
 
--   Bastion host is deployed in a public subnet in Customer's tenancy. Secured access is allowed for Remote Desktop Protocol (RDP) through Internet Gateway and controlled using a security list.
+-   A bastion host can be deployed in a public subnet in the customer's tenancy. Secure Remote Desktop Protocol (RDP) access is allowed through an internet gateway and controlled by security rules.
 
--   The OCVS SDDC environment is allowed to access only from the Bastion host.
+-   Access to the Oracle Cloud VMware Solution SDDC environment should be allowed only from approved administrative entry points, such as the bastion host.
 
 #### OCVS Data Security
 
-This section details Data Security for the virtual machines in the OCVS environment. It also provides details about how encryption works in vSAN and possible options for Data at rest and Data at transit. We have not received any data security requirements from the Customer. Therefore, the below section details out-of-the-box data security standards for OCVS.
+This section describes data security for virtual machines in the Oracle Cloud VMware Solution environment. It explains how encryption works with vSAN and outlines options for data at rest and data in transit. If no customer-specific data security requirements have been received, this section describes the default data security capabilities available with Oracle Cloud VMware Solution.
 
 **vSAN Data-At-Rest**
 
-Oracle Cloud VMware Solution uses VMware vSAN technology for virtual machine storage management. vSAN comes with its own data-at-rest encryption technique. vSAN can encrypt data at rest in the vSAN datastore. Data at rest encryption within vSAN requires an external Key Management Server (KMS) or a vSphere Native Key Provider. vSAN data at rest encryption is out of the scope of this project. However, customers can enable the data-at-rest encryption anytime at cluster provided it meets the required pre-requisite.
+Oracle Cloud VMware Solution uses VMware vSAN technology for virtual machine storage management. vSAN provides data-at-rest encryption for data stored in the vSAN datastore. vSAN data-at-rest encryption requires an external Key Management Server (KMS) or a vSphere Native Key Provider. vSAN data-at-rest encryption is out of scope for this project. However, customers can enable data-at-rest encryption at the cluster level later, provided the required prerequisites are met.
 
 **vSAN Data-in-Transit**
 
-Oracle Cloud VMware Solution uses VMware vSAN technology for virtual machine storage management. vSAN can encrypt data in transit, as it moves across hosts in your vSAN cluster. vSAN can encrypt data in transit across hosts in the cluster. When you enable data-in-transit encryption, vSAN encrypts all data and metadata traffic between hosts. Traffic between data hosts and witness hosts is encrypted. vSAN data encryption in transit is out of the scope of this project. However, the Customer can enable this functionality at the vSAN cluster in OCVS SDDC.
+Oracle Cloud VMware Solution uses VMware vSAN technology for virtual machine storage management. vSAN can encrypt data in transit as it moves between hosts in the vSAN cluster. When data-in-transit encryption is enabled, vSAN encrypts all data and metadata traffic between hosts. Traffic between data hosts and witness hosts is also encrypted. vSAN data-in-transit encryption is out of scope for this project. However, the customer can enable this capability at the vSAN cluster level in the Oracle Cloud VMware Solution SDDC.
 
 **Block Storage Encryption**
 
-OCI Block Storage can be used to scale the storage for DenseIO OCVS deployment and be used as primary storage in the case of Standard Shapes OCVS. OCI Block Volume is presented to the VMware ESXi server as an iSCSI target to store virtual machine files. OCI security features such as KMS, encryption, and vaults apply to VM data stored in OCI Block Volume. OCI Block Volume is mounted as an external Datastore for VMware SDDC by leveraging OCI managed/Customer managed keys for VM data encryption.
+OCI Block Storage can be used to scale storage for DenseIO Oracle Cloud VMware Solution deployments and as primary storage for Standard Shape Oracle Cloud VMware Solution deployments. OCI Block Volumes are presented to VMware ESXi hosts as iSCSI targets for storing virtual machine files. OCI security features such as Key Management, encryption, and Vault apply to virtual machine data stored on OCI Block Volumes. OCI Block Volumes are mounted as external datastores for the VMware SDDC and can use Oracle-managed or customer-managed keys for virtual machine data encryption.
 
 ### Networking
 
-The architecture has the following components:
+The architecture includes the following components:
 
--   **On-premises Network** - This network is the local network used by your organization. It is one of the spokes of the topology.
+-   **On-premises Network** - The local network used by the organization. It is one of the spokes in the topology.
 
--   **Region** - An Oracle Cloud Infrastructure region is a localized geographic area that contains one or more data centers, called availability domains. Regions are independent of other regions, and vast distances can separate them (across countries or even continents).
+-   **Region** - An Oracle Cloud Infrastructure region is a localized geographic area that contains one or more data centers, called availability domains. Regions are independent from one another and can be separated by large geographic distances.
 
--   **Virtual Cloud Network (VCN)** - A VCN is a customizable, private network that you set up in an Oracle Cloud Infrastructure region. Like traditional data center networks, VCNs give you complete control over your network environment. You can segment VCNs into subnets, which can be scoped to a region or an availability domain. Both regional subnets and availability domain-specific subnets can coexist in the same VCN. A subnet can be public or private.
+-   **Virtual Cloud Network (VCN)** - A customizable private network in an Oracle Cloud Infrastructure region. Like traditional data center networks, VCNs provide control over the network environment. VCNs can be segmented into subnets that are regional or availability domain-specific. Both subnet types can coexist in the same VCN, and each subnet can be public or private.
 
--   **Security List** - For each subnet, you can create security rules that specify the source, destination, and type of traffic that must be allowed in and out of the subnet.
+-   **Security List** - A set of subnet-level security rules that specify the source, destination, and type of traffic allowed into and out of the subnet.
 
 -   **Network Security Group (NSG)** - NSGs act as virtual firewalls for your cloud resources. With the zero-trust security model of Oracle Cloud Infrastructure, all traffic is denied, and you can control the network traffic inside a VCN. An NSG consists of a set of ingress and egress security rules that apply to only a specified set of VNICs in a single VCN.
 
--   **Route Table** - Route tables contain rules to route traffic from subnets to destinations outside a VCN, typically through gateways.
+-   **Route Table** - A set of rules that routes traffic from subnets to destinations outside a VCN, typically through gateways.
 
--   **Dynamic Routing Gateway (DRG)** - The DRG is a virtual router that provides a path for private network traffic between a VCN and a network outside the region, such as a VCN in another Oracle Cloud Infrastructure region, an on-premises network, or a network in another cloud provider.
+-   **Dynamic Routing Gateway (DRG)** - A virtual router that provides a private network path between a VCN and networks outside the region, such as another OCI region, an on-premises network, or another cloud provider.
 
--   **Bastion Host** - The bastion host is a compute instance that serves as a secure, controlled entry point to the topology from outside the cloud. The bastion host is provisioned typically in a demilitarized zone (DMZ). It enables you to protect sensitive resources by placing them in private networks that can't be accessed directly from outside the cloud. The topology has a single, known entry point that you can monitor and audit regularly. So, you can avoid exposing the more sensitive components of the topology without compromising access to them.
+-   **Bastion Host** - A compute instance that provides a secure, controlled administrative entry point from outside the cloud. The bastion host is typically provisioned in a demilitarized zone (DMZ). It helps protect sensitive resources by keeping them in private networks that cannot be accessed directly from outside the cloud. This gives the topology a known entry point that can be monitored and audited.
 
 -   **VPN Connect** - VPN Connect provides site-to-site IPSec VPN connectivity between your on-premises network and VCNs in Oracle Cloud Infrastructure. The IPSec protocol suite encrypts IP traffic before the packets are transferred from the source to the destination and decrypts the traffic when it arrives.
 
@@ -486,47 +489,47 @@ The following diagram of a reference architecture shows how to set up a Virtual
 
 ![IPSec VPN](images/vpn.png)
 
-IPSec VPN architecture has the following components:
+The IPSec VPN architecture includes the following components:
 
--   **VPN Connect** - Function that manages IPSec VPN connections to your tenancy.
+-   **VPN Connect** - The OCI service function that manages IPSec VPN connections to the tenancy.
 
--   **Customer-Premises Equipment (CPE)** - An object that represents the network asset that lives in the on-premises network and establishes the VPN connection. Most border firewalls act as the CPE, but a separate device (like an appliance or a server) can be a CPE.
+-   **Customer-Premises Equipment (CPE)** - An object that represents the network asset in the on-premises network that establishes the VPN connection. Most border firewalls can act as the CPE, but a separate appliance or server can also be used.
 
 -   **Internet Protocol Security (IPSec)** - A protocol suite that encrypts IP traffic before packets are transferred from the source to the destination.
 
--   **Tunnel** - Each connection between the CPE and Oracle Cloud Infrastructure.
+-   **Tunnel** - A connection between the CPE and Oracle Cloud Infrastructure.
 
--   **Border Gateway Protocol (BGP) routing** - Allows routes to be learned dynamically. The DRG dynamically learns the routes from your on-premises network. On the Oracle side, the DRG advertises the VCN's subnets.
+-   **Border Gateway Protocol (BGP) routing** - Enables dynamic route learning. The DRG dynamically learns routes from the on-premises network and advertises the VCN subnets from the Oracle side.
 
--   **Static Routing** - When you create the VPN connection, you inform the existing networks on each side. Changes are not learned dynamically.
+-   **Static Routing** - Requires the networks on each side of the VPN connection to be defined manually. Route changes are not learned dynamically.
 
-IPSec VPN will be used to provide for the connection between A Company Making Everything" data center and Oracle OCI Public cloud region for standard day-to-day operational purposes. Based on the current information IPSec connection is already established.
+IPSec VPN will provide connectivity between the A Company Making Everything data center and the Oracle Cloud Infrastructure region for standard day-to-day operational purposes. Based on the current information, the IPSec connection is already established.
 
-##### Fast Connect
+##### FastConnect
 
 The following reference architecture diagram shows how to set up a FastConnect connection between your on-premises network and Virtual Cloud Network (VCN).
 
-![Fast Connect](images/fc.png)
+![FastConnect](images/fc.png)
 
--   **Border Gateway Protocol (BGP) routing** - Allows routes to be learned dynamically. The DRG dynamically learns the routes from your on-premises network. On the Oracle side, the DRG advertises the VCN's subnets.
+-   **Border Gateway Protocol (BGP) routing** - Enables dynamic route learning. The DRG dynamically learns routes from the on-premises network and advertises the VCN subnets from the Oracle side.
 
 -   **Private Peering** - Extends existing infrastructure by using private IP addresses.
 
 -   **Public Peering** - Allows public Oracle Cloud Infrastructure services to be accessed using a private connection instead of the internet.
 
--   **Virtual Circuit** - The private path used to connect on-premises and Oracle Cloud Infrastructure. It can include multiple lines, physical or logical, depending on the requirements and capabilities of the line provider.
+-   **Virtual Circuit** - The private path used to connect on-premises environments and Oracle Cloud Infrastructure. It can include multiple physical or logical lines, depending on the requirements and the provider's capabilities.
 
-Fast Connect will be used to provide for the connection between A Company Making Everything" data center and Oracle OCI Frankfurt cloud region for the period migrations of VMs from on-premise to Oracle cloud. It is a requirement to use Fast Connect at least for the period of workload migration.
+FastConnect will provide connectivity between the A Company Making Everything data center and the selected Oracle Cloud Infrastructure region during virtual machine migration from on-premises VMware to Oracle Cloud. FastConnect is required at least for the duration of workload migration.
 
 ##### OCVS Specific Networking Configuration Within OCI
 
-The Oracle Cloud VMware Solution networking categorizes into Virtual Cloud Networks, Subnets, and VLANs. Each VLAN within VCN is attached to the Network Security Group for network communication and Route Table for routing functionality. Similarly, the subnet created as an outcome of the SDDC provisioning operation is attached to Security List and Route Table.
+Oracle Cloud VMware Solution networking is organized into virtual cloud networks, subnets, and VLANs. Each VLAN within the VCN is attached to a network security group for traffic control and a route table for routing. Similarly, the subnet created during the SDDC provisioning workflow is attached to a security list and route table.
 
 ![OCVS detailed networking overview and components](images/net_overview.png)
 
 ##### OCI Virtual Cloud Network (VCN) for OCVS
 
-All the resources in OCVS/SDDC architecture are in a single VCN. For VMware SDDC we need at least /24 network CIDR but recommended is to have a dedicated /16 VCN CIDR block that can accommodate future scaling of the networks.
+All Oracle Cloud VMware Solution SDDC resources are deployed in a single VCN. A VMware SDDC requires at least a /24 network CIDR. A dedicated /16 VCN CIDR block is recommended to support future network growth.
 
 | VCN                      | CIDR Range              |
 |:-------------------------|:------------------------|
@@ -534,19 +537,19 @@ All the resources in OCVS/SDDC architecture are in a single VCN. For VMware SDDC
 | SDDC CIDR                | 10.0.0.0/21             |
 | Workload CIDR (Optional) | 192.168.10.0/24 (NSX-T) |
 
-The OCVS networking resources such as Subnet, VLANs, Network Security Groups (NSG), Route Tables, and Gateways are the result of OCVS SDDC provisioning operation. The network CIDR ranges for the management VLANs are solely dependent on the size of the SDDC CIDR. The network design considerations should be carefully assessed before provisioning the OCVS environment.
+Oracle Cloud VMware Solution networking resources, including subnets, VLANs, network security groups, route tables, and gateways, are created as part of the SDDC provisioning workflow. The CIDR ranges for management VLANs depend on the size of the SDDC CIDR. Network design considerations should be assessed carefully before provisioning the Oracle Cloud VMware Solution environment.
 
 ### Operating Model, Monitoring, and Management
 
-This section describes the details of management and monitoring capabilities available out of the box from Oracle Cloud VMware Solution. Oracle Cloud VMware Solution offers VMware vRealize Operations (vROPS) manager as a monitoring tool integrated with OCVS vCenter server. VMware vROPS is pre-integrated with the vCenter server and offers a dashboard for monitoring the entire VMware SDDC farm. The vROPS has a predefined matrix for availability, performance, and capacity which will help customers for their day-to-day operations. Below are some of the benefits of vROPS.
+This section describes management and monitoring capabilities for Oracle Cloud VMware Solution. Customers can use VMware Aria Operations, formerly vRealize Operations, or other compatible operations tooling to monitor the Oracle Cloud VMware Solution environment, subject to licensing and entitlement. Operations tooling can provide dashboards and metrics for availability, performance, and capacity to support day-to-day operations. The following are examples of common benefits.
 
 -   Application-aware monitoring across SDDC and multiple clouds.
 -   Cloud Planning, capacity optimization, and compliance.
 -   Automated and proactive workloads management.
 
-Customer can also leverage their existing on-premises vROPS implementation to extend the monitoring capabilities to OCVS. In addition, customers can also leverage their existing tooling and automation with OCVS SDDC. For example, products such as VMware vRealize Log Insight, VMware vRealize automation, and others.
+Customers can also extend existing on-premises operations tooling to Oracle Cloud VMware Solution where supported. Existing automation and logging tools can also be used with the Oracle Cloud VMware Solution SDDC, such as VMware Aria Operations for Logs, formerly vRealize Log Insight, and VMware Aria Automation, formerly vRealize Automation.
 
-**Important note:** Customers will need to bring their own license to use vRealize Operations Manager. The vROPS is also available as a SaaS subscription from VMware which can be used to monitor the OCVS environment in VMware Cloud.
+**Important note:** Customers must bring or procure the required licenses for VMware operations tooling. Licensing, entitlement, support, and SaaS availability must be validated with Broadcom or an authorized VMware partner.
 
 #### OCVS Support
 
@@ -555,47 +558,45 @@ Customer can also leverage their existing on-premises vROPS implementation to ex
 
 ### OCVS Migration
 
-This section describes the Migration options and tools used for the migration of mission-critical workloads to OCVS.
+This section describes the migration options and tools used to migrate mission-critical workloads to Oracle Cloud VMware Solution.
 
-VMware HCX is an application mobility platform that allows you to migrate VMs from an on-premises VMware environment to the OCVS SDDC. The HCX comes with two different types of license, HCX Advanced offered for free and the HCX Enterprise as an additional SKU which can be enabled from the OCI console on a monthly subscription basis.
+VMware HCX is an application mobility platform that enables migration and workload rebalancing between an on-premises VMware environment and an Oracle Cloud VMware Solution SDDC. HCX licensing must be reviewed as part of the customer's VMware BYOL position. The licensing and entitlement model can vary by VMware software bundle, Oracle Cloud VMware Solution shape, and commercial agreement. Do not assume that HCX or other VMware components are license-included with Oracle Cloud VMware Solution.
 
-According to the feature requirements, the HCX license type should be carefully evaluated. For more details about the HCX licensing comparison, refer to the document link below.
+Evaluate the HCX license level against the required migration and mobility features before selecting the migration approach. For more information about HCX license differences, see the following documentation:
 
 [VMware HCX Licensing](https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/hcx/vmw-hcx-licensing-and-packaging-solution-overview.pdf)
 
-**Please note:** If you are using OCVS with Standard Shapes, then the HCX enterprise is included in the subscription and no additional cost is required.
-
-VMware HCX is a preferred way of migrating VMWare Workloads to OCVS. However, in some cases, you should consider using other third-party tools.
+**Please note:** Check the VMware interoperability matrix to confirm VMware HCX compatibility with the source vSphere environment.
 
-The HCX offers different key features along with various migration options.
+VMware HCX is a common approach for migrating VMware workloads to Oracle Cloud VMware Solution. However, third-party tools such as Zerto, RackWare, and Veeam can also be evaluated where they better align with customer migration, replication, recovery, licensing, or operational requirements.
 
-**Please Note:** Please check the VMware interoperability matrix for version compatibility of VMware HCX with the source vSphere environment.
+HCX offers different key features and migration options, subject to licensing and entitlement.
 
 #### Migration Architecture with OCVS
 
-The architecture diagram shows the overall HCX architecture.
+The architecture diagram shows the overall HCX migration architecture.
 
 ![OCVS Migration Architecture using HCX](images/HCXmigrationarchitecture.png)
 
 #### HCX Features and Migration Options
 
-The below list of features is included with the default HCX advanced license offered with an OCVS subscription without any additional cost.
+The following features are commonly associated with HCX migration designs. Confirm availability against the customer's VMware license entitlements and the supported HCX version before implementation.
 
 -   Migration
--   Disaster Recovery
+-   Disaster Recovery, subject to lifecycle and support considerations
 -   Network Extension
 
 ##### Migration Options with VMware HCX
 
-**vMotion** - Allow live migration of the VM from source to target (OCVS). It is a serial migration and does not allow parallel live migration of more than 1 VM with an HCX advanced license. Use HCX Enterprise, if you would like to migrate VMs live and in parallel.
+**vMotion** - Allows live migration of a virtual machine from the source environment to Oracle Cloud VMware Solution. Depending on HCX license entitlement and version, this may be a serial migration and may not allow parallel live migration of multiple virtual machines. Confirm HCX capabilities and licensing before selecting this method.
 
-**Bulk Migration** - Parallel migration of multiple VMs. The VMs incur downtime equivalent to the restart of the VM at OCVS. The source VM will be preserved and powered off at the source. When there are no changes at the source, the HCX will power on the target VM and shut down the source. The failover operation is not controlled by the end user. The HCX bulk migration can be used with the HCX advanced license.
+**Bulk Migration** - Enables parallel migration of multiple virtual machines. The virtual machines incur downtime equivalent to the restart of the virtual machine on Oracle Cloud VMware Solution. The source virtual machine is preserved and powered off at the source. When there are no changes at the source, HCX powers on the target virtual machine and shuts down the source. The failover operation is orchestrated by HCX.
 
-**Disaster Recovery** - Works on the same technology as bulk migration but allows you to replicate on different RPO with controlled failover, re-protect, and fallback operations.
+**Disaster Recovery** - Uses similar replication technology to bulk migration and supports replication with configurable RPOs, controlled failover, reprotection, and failback operations. According to Broadcom HCX release notes, HCX Disaster Recovery has been deprecated and is planned for removal in a future release. It should not be selected as the strategic disaster recovery platform for new enterprise designs unless the customer has explicitly accepted the lifecycle and support implications. For enterprise disaster recovery and business continuity, evaluate VMware Site Recovery Manager as part of the [VMware Live Recovery](https://www.vmware.com/products/cloud-infrastructure/advanced-services/live-recovery) portfolio, or third-party solutions such as Zerto, RackWare, and Veeam.
 
 ##### Network Extension
 
-This is a feature that allows you to perform L2 VLAN extension from on-premises to OCVS. The network extension is used for preserving the same IP address for the migrated VMs. The requirement of network extension should be carefully evaluated.
+Network Extension enables L2 network extension from on-premises environments to Oracle Cloud VMware Solution. It is commonly used to preserve the same IP addresses for migrated virtual machines. The requirement for network extension should be carefully evaluated because it can affect migration sequencing, routing, security controls, latency, operations, and rollback planning.
 
 ## Sizing and Bill of Materials
 
@@ -617,22 +618,22 @@ Sample sizing of the OCVS environment is depicted in the table below.
 
 -   The calculation is based on the current compute and storage resources. The 4-node cluster can satisfy the required resources.
 -   1 host failure will allow the customer a rebuild capacity in case of failure.
--   This is a mixed environment between physical nodes and VMWare VMs, the oversubscription details are not relevant to the proposed sizing.
--   We have considered the 1:2 core to vCPU ratio which offers the best optimum performance for converted physical workloads as well as VMWare workloads.
--   The OCVS compute offers flexible DenseIO and Standard Shapes for sizing the current capacity requirements.
--   It is recommended to start with 4 node cluster and add the servers on demand as needed.
--   The Block storage with OCVS DenseIO allows you to scale the storage without adding additional server capacity.
--   OCVS deployment with the standard shape uses Block Storage as a primary storage option.
+-   This is a mixed environment between physical nodes and VMware virtual machines; oversubscription details are not relevant to the proposed sizing.
+-   We have considered a 1:2 core-to-vCPU ratio, which provides strong performance for converted physical workloads and VMware workloads.
+-   Oracle Cloud VMware Solution compute offers flexible DenseIO and Standard Shapes for sizing current capacity requirements.
+-   It is recommended to start with a 4-node cluster and add servers on demand as needed.
+-   Block Storage with Oracle Cloud VMware Solution DenseIO allows storage to scale without adding server capacity.
+-   Oracle Cloud VMware Solution deployments with Standard Shapes use Block Storage as the primary storage option.
 
 **BoQ Notes:**
 
-1.  Bring Your Own License (BYOL) of existing On-Premises VMware licenses to OCVS is not supported.
-2.  VMware HCX Advanced is offered free with OCVS. However, the HCX enterprise license is a separate SKU and can be enabled/disabled from the OCI console based on the extended functionality requirements for migration.
-3.  If you are using OCVS with Standard Shape and then the HCX enterprise license is included in the subscription and no additional cost is required.
+1.  New Oracle Cloud VMware Solution capacity must use the BYOL model. Existing eligible VMware VCF subscription entitlements must be validated with Broadcom or an authorized VMware partner, registered in Oracle Cloud VMware Solution License Management, allocated to the target OCI region, and selected during SDDC provisioning, workload cluster creation, or ESXi host scale-out.
+2.  Long-term license-included Oracle Cloud VMware Solution SKUs, including monthly, 1-year, and 3-year license-included options, were discontinued effective March 22, 2026. New SDDCs could be deployed using the license-included model until March 21, 2026, and existing SDDCs could continue scaling out with hourly license-included hosts until May 20, 2026. After these dates, all new Oracle Cloud VMware Solution capacity must be provisioned using BYOL.
+3.  HCX, VMware Live Recovery, Site Recovery Manager, Veeam, Zerto, RackWare, and any other migration, disaster recovery, backup, or operations tooling must be licensed according to the customer's entitlement and vendor agreement. Do not assume any VMware component is included with Oracle Cloud VMware Solution unless validated during commercial and technical discovery.
 
 | Part \# | Product Name                                     | Metric                                  | Quantity |
 |:--------|:-------------------------------------------------|:----------------------------------------|:---------|
-| B92386  | Oracle Cloud VMware Solution 1 Year Subscription | OCPU per Hour                           | 208      |
+| XXXXXX  | Oracle Cloud VMware Solution BYOL capacity       | OCPU per Hour                           | 208      |
 | XXXXXX  | Windows Bastion Host VM.Standard.2.2             | OCPU Per Hour                           | 1        |
 | B91628  | OCI Object Storage                               | Gb per month                            | 52000    |
 | B91627  | OCI Object Storage Requests                      | 10K requests per month (first 50k free) | 1        |
@@ -683,49 +684,49 @@ The following are the project deliverables:
 
 ### Included Activities
 
-Following high-level scope lift scope:
+The high-level Lift scope includes:
 
 -   Deploy VMware SDDC as per design.
--   Assist in setting up Fast Connect connection.
+-   Assist in setting up the FastConnect connection.
 -   Agreed scope of workload migration.
 
 The following high-level Activities will be carried out by Lift:
 
 -   OCI Foundation Setup required for OCVS deployment in the decided Region with Bastion Service
--   One Fast Connect setup between on-premises and OCI before migration
+-   One FastConnect setup between on-premises and OCI before migration.
 -   Provision one Compute Windows Bastion Host to manage OCVS environment
--   Single OCVS Setup on OCI with the latest Version with an agreed number of ESXi host\
--   Configuration On-Prem Connectivity for VMware Migration to OCVS Environment
--   Configure and Implement VMware HCX required for migration and network extension.
+-   Single Oracle Cloud VMware Solution setup on OCI with the agreed number of ESXi hosts.
+-   Configuration of on-premises connectivity for VMware migration to the Oracle Cloud VMware Solution environment.
+-   Configure and implement VMware HCX required for migration and network extension, subject to customer licensing and entitlement.
 -   Configure and implement the agreed backup solution as part of the design.
--   Validate with test VM Migration of Source VM to OCVS using VMware HCX
+-   Validate migration with a test source virtual machine migration to Oracle Cloud VMware Solution using VMware HCX.
 -   Any additional tooling to support overall migration as agreed in the design.
 
 ### Recommended Activities
 
--   HCX Setup between on-premises and OCVS
+-   HCX setup between on-premises and Oracle Cloud VMware Solution, subject to customer licensing and entitlement.
 -   DR/HA setup
--   IP Sec VPN setup between on-premises to OCI
+-   IPSec VPN setup between on-premises and OCI.
 -   Installation and configuration of custom or third-party applications and operating systems on deployed virtual machines.
 -   Rewiring/Integration of application and database is the customer's responsibility
--   Creation of Image template on OCVS setup.
--   Migration of Windows Server 2003 Enterprise Physical servers to OCVS
--   Source Server IPs retention of the migrated VMs at OCI/OCVS Target
+-   Creation of image templates on Oracle Cloud VMware Solution.
+-   Migration of Windows Server 2003 Enterprise physical servers to Oracle Cloud VMware Solution.
+-   Source server IP retention for migrated virtual machines at the OCI or Oracle Cloud VMware Solution target.
 -   Active Directory and DNS Server Setup in OCI
 -   Operating system administration including the operating system itself or any operating system features or components. Management of any required changes to virtual machines, operating systems, custom or third-party applications, databases, and administration of general network changes within Customer control.
 -   Remediation work associated with any problems resulting from the content, completeness, accuracy, and consistency of any data, materials, or information supplied by the Customer
 -   Any new or existing customizations, features modifications, and/or integration with other products
 -   Troubleshooting of existing open issues, including the performance of applications
--   Installation and configuration of third-party software or other technical services that do not apply to OCVS.
+-   Installation and configuration of third-party software or other technical services that do not apply to Oracle Cloud VMware Solution.
 -   Configuration of VMware products used for the service other than those implemented for the mutually agreed use cases.
 -   Customer solution training other than the defined knowledge transfer session, Training on deployed products and Cloud Services
--   Backup configuration of the third-party tool with OCVS.
--   Physical servers from Customer on-premises IT infrastructure.
+-   Backup configuration of third-party tools with Oracle Cloud VMware Solution.
+-   Physical servers from the customer's on-premises IT infrastructure.
 -   IDCS integration with Active Directory for Customer's OCI tenancy.
 -   24/7 Support coverage and Post Migration support
--   Load Testing, Performance benchmarking, testing & tuning of any component in the solution.
+-   Load testing, performance benchmarking, testing, and tuning of any component in the solution.
 -   Architecture and design changes, after the agreed design.
--   Operational Monitoring & Management design
+-   Operational monitoring and management design.
 -   Third Party Security and Monitoring tools implementation or integration
 -   Server Hardening, Audit certification, Vulnerability Assessment, and Penetration Testing
 -   Program management (outside of Lift scope), Business readiness, cut-over planning.
@@ -741,12 +742,12 @@ The table below provides a responsibility matrix between Oracle and Customer, wi
 | 1   | Project kick-off                                                          | R A    | C        |
 | 2   | Project Management                                                        | R      | A        |
 | 3   | OCI Access                                                                | I      | R A      |
-| 4   | OCI Foundation required setup for OCVS and Bastion Host provisioning      | R A    | C        |
-| 5   | Fast connect setup between on-premises and OCI                            | R A    | CA       |
-| 6   | Deployment of OCVS VMware SDDC                                            | R      | C        |
-| 7   | Migration of Supported Source Servers from customer sites to OCVS         | R A    | C        |
+| 4   | OCI foundation setup required for Oracle Cloud VMware Solution and bastion host provisioning | R A    | C        |
+| 5   | FastConnect setup between on-premises and OCI                             | R A    | CA       |
+| 6   | Deployment of Oracle Cloud VMware Solution SDDC                           | R      | C        |
+| 7   | Migration of supported source servers from customer sites to Oracle Cloud VMware Solution | R A    | C        |
 | 8   | Installation and configuration of the backup tools as agreed in the scope | R A    | C        |
-| 9   | Perform Functional testing & Validation of migrated VMs                   | I      | RA       |
+| 9   | Perform functional testing and validation of migrated VMs                 | I      | RA       |
 
 R- Responsible, I- Informed, A- Accountable, C- Consulted
 
@@ -761,29 +762,29 @@ The participation of the following Customer stakeholders is required for the Ser
 ### Assumptions
 
 -   OCI Admin Access is provided to access the tenancy.
--   The Fast Connect link with a minimum of 1 Gbps bandwidth is available beforehand for implementation to connect to Customer locations. OCI Fast Connect will be set up during the migration to handle the size of the workload to be migrated.
+-   The FastConnect link with a minimum of 1 Gbps bandwidth is available before implementation to connect to customer locations. OCI FastConnect will be set up during the migration to handle the size of the workload to be migrated.
 -   Connection bandwidth available for data transfer during the migration will be available and will not depend (be limited) on a specific time window.
--   Provided Lift effort is based on migration execution over Fast Connect link of min 1 Gbps.
+-   The provided Lift effort is based on migration execution over a FastConnect link of at least 1 Gbps.
 -   Post migration, Customer branches will connect to the environment using IPSec VPN.
--   The CIDR which will be used for OCVS provisioning does not overlap with current on-premises network ranges and it is assumed that there is no requirement to extend networks between on-premises & cloud environments.
+-   The CIDR used for Oracle Cloud VMware Solution provisioning does not overlap with current on-premises network ranges, and it is assumed that there is no requirement to extend networks between on-premises and cloud environments unless explicitly included in scope.
 -   There will be no dependency of the Lift migration project on a larger project context, i.e. timing and/or other project context.
--   OCVS will be deployed in the same tenancy in a dedicated compartment.
+-   Oracle Cloud VMware Solution will be deployed in the same tenancy in a dedicated compartment.
 -   Source Application/Database Source VMs are non-clustered.
 -   Inter-dependency of Application/database to be shared.
 -   Any downtime window required during migration and cut-over phases will be arranged by the Customer.
 -   There are no Microsoft clusters with RDM attachments.
--   There are no licensing constraints from Microsoft or any other software vendors. for example, Microsoft SQL Enterprise host-based unlimited license.
+-   There are no licensing constraints from Microsoft, Broadcom, VMware, or any other software vendors that would prevent migration to Oracle Cloud VMware Solution.
 -   The supplied sizing details of the cores are vCPUs and not actual physical cores.
--   Customer will take care of the integration work required for different services post migrations of VMware workloads.
+-   Customer will take care of the integration work required for different services after VMware workload migration.
 -   Customer will have the necessary Oracle Support (MoS) contract for all the products that may/will be used during this project.
 -   Customer will be managing any other 3rd party vendors or suppliers.
--   Customer will have adequate licenses for all the products that may/will be used during this project.
--   Enough service limit for VM/OCVS shape in Customer tenancy is available for provisioning.
--   Required integration of Active Directory and DNS infrastructure will be configured by the Customer for the migrated workload to OCVS.
--   Sequence of VM migration to be shared for each phase and agreed upon before delivery phase to accomplish delivery Schedule.
+-   Customer will have adequate licenses for all products used during this project, including VMware, migration, backup, monitoring, operating system, and application software.
+-   Sufficient service limits for virtual machines and Oracle Cloud VMware Solution shapes are available in the customer tenancy for provisioning.
+-   Required integration of Active Directory and DNS infrastructure will be configured by the customer for the migrated workload to Oracle Cloud VMware Solution.
+-   The virtual machine migration sequence will be shared for each phase and agreed before the delivery phase to meet the delivery schedule.
 -   It is assumed that all work will be done remotely and within either central European time or Indian standard time normal office working hours.
--   Any problems, issues, errors, and anomalies to be addressed through MOS SRs & will continue to be owned by the Customer.
--   Details and Naming convention will be provided for OCI resources.
+-   Any problems, issues, errors, and anomalies will be addressed through My Oracle Support service requests and will continue to be owned by the customer.
+-   Details and naming conventions will be provided for OCI resources.
 -   Any additional effort outside of the scope of this proposal will be managed by change control and mutually agreed upon by both Oracle and Customer.
 
 ### Obligations
@@ -791,9 +792,9 @@ The participation of the following Customer stakeholders is required for the Ser
 -   The Oracle Lift team will have appropriate access to A Company Making Everything OCI tenancy and on-premises IT environment for implementation.
 -   A Company Making Everything will have purchased the appropriate Universal Credits for the services required for the project.
 -   A Company Making Everything will have the necessary Oracle Support and Cloud services contracts for all the products and services that will be used during this project.
--   A Company Making Everything will ensure the appropriate product training has been obtained to support the implementation. The lift provides post-migration knowledge transfer; however, it does not replace basic cloud products/services training.
--   A Company Making Everything is responsible to certify the compatibility of their applications/database components used on the target platform & DB versions.
--   A Company Making Everything will be responsible for the Application testing, which should be completed within the agreed testing window. Post-migration application issues will be handled by A Company Making Everything Oracle Cloud Lift team will perform basic DB tests.
+-   A Company Making Everything will ensure the appropriate product training has been obtained to support the implementation. Lift provides post-migration knowledge transfer; however, it does not replace basic cloud product or service training.
+-   A Company Making Everything is responsible for certifying the compatibility of its application and database components on the target platform and database versions.
+-   A Company Making Everything will be responsible for application testing, which should be completed within the agreed testing window. Post-migration application issues will be handled by A Company Making Everything. The Oracle Cloud Lift team will perform basic database tests where included in scope.
 -   A Company Making Everything will manage any third-party suppliers or vendors.
 
 ### Risks
@@ -803,7 +804,7 @@ The participation of the following Customer stakeholders is required for the Ser
 | RI01    | Delay in FastConnect Provisioning will impact overall project timeline                                                 | Pre-plan Fastconnect provisioning requirements.                                                                   |
 | RI02    | Incompatible or unsupported workload versions in the current environment can prevent migration                         | Identify version incompatibilities and follow appropriate tooling and migration methodologies                     |
 | RI03    | VMware workloads with physical RDM attached disks cannot be migrated using HCX                                         | Identify such workloads and use different migration methodology                                                   |
-| RI04    | No NSX environment in the current setup can only allow one-way migration from on-premises to OCVS                      | Do not plan a hybrid strategy where the workloads need to be migrated back to On-Premises SDDC                    |
+| RI04    | No NSX environment in the current setup can limit migration to a one-way movement from on-premises to Oracle Cloud VMware Solution | Do not plan a hybrid strategy where workloads need to be migrated back to the on-premises SDDC                    |
 | RI05    | Licensing constraints from software vendors can produce compliance issues preventing migration to OCVS                 | Identify any such licensing requirement beforehand and discuss with respective vendors to address the requirement |
 | RI06    | Oracle Apps and DBs running in a VMware environment can produce compliance and technical issues moving to OCVS         | Identify Oracle workloads and migrate them to OCI native instead of OCVS                                          |
 | RI07    | Current backup data cannot be migrated to OCVS                                                                         | Post migration a customer can choose a new backup strategy and have new copies of backup data in Oracle Cloud     |
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/files/images/HCXmigrationarchitecture.png b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/files/images/HCXmigrationarchitecture.png
index 5c571126c..43c85d00a 100644
Binary files a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/files/images/HCXmigrationarchitecture.png and b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/files/images/HCXmigrationarchitecture.png differ
diff --git a/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/files/images/HCXmigrationarchitecture.svg b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/files/images/HCXmigrationarchitecture.svg
new file mode 100644
index 000000000..3055bb5c3
--- /dev/null
+++ b/cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/vmware-migration-solution-definition/files/images/HCXmigrationarchitecture.svg
@@ -0,0 +1,177 @@
+<svg xmlns="http://www.w3.org/2000/svg" width="1600" height="900" viewBox="0 0 1600 900" role="img" aria-labelledby="title desc">
+  <title id="title">Oracle Cloud VMware Solution HCX Migration Architecture</title>
+  <desc id="desc">Customer-facing HCX migration architecture showing on-premises VMware, Oracle Cloud VMware Solution, HCX Connector, HCX Cloud Manager, Service Mesh creation, migration service appliances, network connectivity, and migration flows.</desc>
+  <defs>
+    <style>
+      .bg { fill: #f7f9fc; }
+      .zone { fill: #eaf2ff; stroke: #5a7fb8; stroke-width: 2; }
+      .zone-title { font: 700 18px Arial, sans-serif; fill: #111827; }
+      .section-title { font: 700 15px Arial, sans-serif; fill: #111827; }
+      .label { font: 500 14px Arial, sans-serif; fill: #1f2937; }
+      .small { font: 500 12px Arial, sans-serif; fill: #374151; }
+      .tiny { font: 500 11px Arial, sans-serif; fill: #374151; }
+      .note { font: 600 12px Arial, sans-serif; fill: #374151; }
+      .box { fill: #ffffff; stroke: #94a3b8; stroke-width: 1.5; rx: 8; }
+      .box-blue { fill: #0b5cab; stroke: #073b73; stroke-width: 1.5; rx: 8; }
+      .box-blue-text { font: 700 14px Arial, sans-serif; fill: #ffffff; }
+      .box-green { fill: #e9f8ef; stroke: #1f8f4f; stroke-width: 1.5; rx: 8; }
+      .box-orange { fill: #fff4e5; stroke: #d97706; stroke-width: 1.5; rx: 8; }
+      .box-neutral { fill: #ffffff; stroke: #cbd5e1; stroke-width: 1.5; rx: 8; }
+      .line { stroke: #344054; stroke-width: 2; fill: none; }
+      .line-dash { stroke: #64748b; stroke-width: 2; stroke-dasharray: 8 6; fill: none; }
+      .line-blue { stroke: #0b5cab; stroke-width: 3; fill: none; }
+      .line-green { stroke: #15803d; stroke-width: 3; fill: none; }
+      .line-orange { stroke: #d97706; stroke-width: 3; fill: none; }
+      .vm { fill: #0f766e; }
+      .host { fill: #f59e0b; stroke: #b45309; stroke-width: 1; }
+      .host-base { fill: #dbeafe; }
+      .legend { fill: #ffffff; stroke: #cbd5e1; stroke-width: 1.2; rx: 8; }
+    </style>
+    <marker id="arrow" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="8" markerHeight="8" orient="auto-start-reverse">
+      <path d="M 0 0 L 10 5 L 0 10 z" fill="#344054"/>
+    </marker>
+    <marker id="arrow-blue" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="8" markerHeight="8" orient="auto-start-reverse">
+      <path d="M 0 0 L 10 5 L 0 10 z" fill="#0b5cab"/>
+    </marker>
+    <marker id="arrow-green" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="8" markerHeight="8" orient="auto-start-reverse">
+      <path d="M 0 0 L 10 5 L 0 10 z" fill="#15803d"/>
+    </marker>
+    <marker id="arrow-orange" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="8" markerHeight="8" orient="auto-start-reverse">
+      <path d="M 0 0 L 10 5 L 0 10 z" fill="#d97706"/>
+    </marker>
+  </defs>
+
+  <rect class="bg" width="1600" height="900"/>
+
+  <text x="800" y="34" text-anchor="middle" font-family="Arial, sans-serif" font-size="24" font-weight="700" fill="#111827">VMware HCX Migration Architecture for Oracle Cloud VMware Solution</text>
+  <text x="800" y="58" text-anchor="middle" class="small">HCX Connector and HCX Cloud Manager create a Service Mesh for workload mobility</text>
+
+  <rect x="35" y="96" width="560" height="640" class="zone"/>
+  <text x="315" y="126" text-anchor="middle" class="zone-title">On-Premises VMware Data Center</text>
+  <text x="315" y="148" text-anchor="middle" class="small">vCenter, NSX/VDS, ESXi clusters, workloads</text>
+
+  <rect x="1005" y="96" width="560" height="640" class="zone"/>
+  <text x="1285" y="126" text-anchor="middle" class="zone-title">OCI Region - Oracle Cloud VMware Solution</text>
+  <text x="1285" y="148" text-anchor="middle" class="small">VMware SDDC on OCI Bare Metal, VCN/VLANs, NSX overlay</text>
+
+  <rect x="640" y="98" width="320" height="58" class="box-neutral"/>
+  <text x="800" y="122" text-anchor="middle" class="section-title">Internet Access for HCX Lifecycle</text>
+  <text x="800" y="144" text-anchor="middle" class="tiny">Activation and updates through VMware/Broadcom endpoints</text>
+
+  <rect x="205" y="178" width="210" height="92" class="box"/>
+  <text x="310" y="205" text-anchor="middle" class="section-title">HCX Connector</text>
+  <text x="310" y="228" text-anchor="middle" class="small">Customer-managed appliance</text>
+  <text x="310" y="248" text-anchor="middle" class="tiny">Creates Service Mesh with</text>
+  <text x="310" y="263" text-anchor="middle" class="tiny">HCX Cloud Manager</text>
+
+  <rect x="1185" y="178" width="210" height="92" class="box"/>
+  <text x="1290" y="205" text-anchor="middle" class="section-title">HCX Cloud Manager</text>
+  <text x="1290" y="228" text-anchor="middle" class="small">Enabled in OCVS SDDC</text>
+  <text x="1290" y="248" text-anchor="middle" class="tiny">Creates Service Mesh with</text>
+  <text x="1290" y="263" text-anchor="middle" class="tiny">HCX Connector</text>
+
+  <path class="line-dash" marker-end="url(#arrow)" d="M415 196 L640 127"/>
+  <path class="line-dash" marker-end="url(#arrow)" d="M1185 196 L960 127"/>
+
+  <rect x="652" y="286" width="296" height="58" class="box-blue"/>
+  <text x="800" y="311" text-anchor="middle" class="box-blue-text">Site Pairing</text>
+  <text x="800" y="331" text-anchor="middle" font-family="Arial, sans-serif" font-size="12" font-weight="600" fill="#dbeafe">Secure pairing between HCX sites</text>
+  <path class="line" marker-end="url(#arrow)" d="M415 224 L652 315"/>
+  <path class="line" marker-end="url(#arrow)" d="M948 315 L1185 224"/>
+
+  <rect x="596" y="384" width="408" height="74" class="box-blue"/>
+  <text x="800" y="411" text-anchor="middle" class="box-blue-text">Service Mesh</text>
+  <text x="800" y="431" text-anchor="middle" font-family="Arial, sans-serif" font-size="12" font-weight="600" fill="#dbeafe">Created by HCX Connector and HCX Cloud Manager</text>
+  <text x="800" y="447" text-anchor="middle" font-family="Arial, sans-serif" font-size="12" font-weight="600" fill="#dbeafe">Deploys paired migration service appliances</text>
+
+  <rect x="424" y="300" width="118" height="214" class="box-green"/>
+  <text x="483" y="322" text-anchor="middle" class="section-title">Migration</text>
+  <text x="483" y="340" text-anchor="middle" class="section-title">Services</text>
+  <rect x="446" y="346" width="74" height="42" class="box"/>
+  <text x="483" y="372" text-anchor="middle" class="note">NE</text>
+  <rect x="446" y="404" width="74" height="42" class="box"/>
+  <text x="483" y="430" text-anchor="middle" class="note">IX</text>
+  <rect x="446" y="462" width="74" height="42" class="box"/>
+  <text x="483" y="488" text-anchor="middle" class="note">WO</text>
+
+  <rect x="1058" y="300" width="118" height="214" class="box-green"/>
+  <text x="1117" y="322" text-anchor="middle" class="section-title">Migration</text>
+  <text x="1117" y="340" text-anchor="middle" class="section-title">Services</text>
+  <rect x="1080" y="346" width="74" height="42" class="box"/>
+  <text x="1117" y="372" text-anchor="middle" class="note">NE</text>
+  <rect x="1080" y="404" width="74" height="42" class="box"/>
+  <text x="1117" y="430" text-anchor="middle" class="note">IX</text>
+  <rect x="1080" y="462" width="74" height="42" class="box"/>
+  <text x="1117" y="488" text-anchor="middle" class="note">WO</text>
+
+  <path class="line-blue" marker-end="url(#arrow-blue)" d="M542 367 L596 414"/>
+  <path class="line-blue" marker-end="url(#arrow-blue)" d="M1004 414 L1058 367"/>
+  <path class="line-blue" marker-end="url(#arrow-blue)" d="M542 425 L596 421"/>
+  <path class="line-blue" marker-end="url(#arrow-blue)" d="M1004 421 L1058 425"/>
+  <path class="line-blue" marker-end="url(#arrow-blue)" d="M542 483 L596 429"/>
+  <path class="line-blue" marker-end="url(#arrow-blue)" d="M1004 429 L1058 483"/>
+
+  <rect x="608" y="492" width="384" height="40" class="box"/>
+  <text x="800" y="515" text-anchor="middle" class="label">WAN / FastConnect / IPSec VPN</text>
+
+  <rect x="84" y="364" width="248" height="92" class="box"/>
+  <text x="208" y="391" text-anchor="middle" class="section-title">vCenter / NSX / VDS</text>
+  <text x="208" y="414" text-anchor="middle" class="small">Inventory, networks, migration source</text>
+  <text x="208" y="435" text-anchor="middle" class="tiny">Manages source ESXi clusters</text>
+
+  <rect x="1268" y="364" width="248" height="92" class="box"/>
+  <text x="1392" y="391" text-anchor="middle" class="section-title">vCenter / NSX-T</text>
+  <text x="1392" y="414" text-anchor="middle" class="small">Target SDDC inventory and overlays</text>
+  <text x="1392" y="435" text-anchor="middle" class="tiny">Manages target ESXi clusters</text>
+
+  <path class="line-dash" d="M208 456 L208 552"/>
+  <path class="line-dash" d="M1392 456 L1392 552"/>
+
+  <rect x="78" y="552" width="450" height="130" class="box"/>
+  <text x="303" y="576" text-anchor="middle" class="section-title">Source ESXi Clusters and Workloads</text>
+  <g transform="translate(104 596)">
+    <polygon class="host-base" points="0,42 92,42 76,82 16,82"/>
+    <rect class="host" x="0" y="16" width="92" height="26"/>
+    <text x="46" y="34" text-anchor="middle" font-family="Arial, sans-serif" font-size="12" font-weight="700" fill="#ffffff">ESXi</text>
+    <rect class="vm" x="8" y="0" width="18" height="14"/><rect class="vm" x="32" y="0" width="18" height="14"/><rect class="vm" x="56" y="0" width="18" height="14"/>
+  </g>
+  <g transform="translate(250 596)">
+    <polygon class="host-base" points="0,42 92,42 76,82 16,82"/>
+    <rect class="host" x="0" y="16" width="92" height="26"/>
+    <text x="46" y="34" text-anchor="middle" font-family="Arial, sans-serif" font-size="12" font-weight="700" fill="#ffffff">ESXi</text>
+    <rect class="vm" x="8" y="0" width="18" height="14"/><rect class="vm" x="32" y="0" width="18" height="14"/><rect class="vm" x="56" y="0" width="18" height="14"/>
+  </g>
+  <g transform="translate(396 596)">
+    <polygon class="host-base" points="0,42 92,42 76,82 16,82"/>
+    <rect class="host" x="0" y="16" width="92" height="26"/>
+    <text x="46" y="34" text-anchor="middle" font-family="Arial, sans-serif" font-size="12" font-weight="700" fill="#ffffff">ESXi</text>
+    <rect class="vm" x="8" y="0" width="18" height="14"/><rect class="vm" x="32" y="0" width="18" height="14"/><rect class="vm" x="56" y="0" width="18" height="14"/>
+  </g>
+
+  <rect x="1072" y="552" width="450" height="130" class="box"/>
+  <text x="1297" y="576" text-anchor="middle" class="section-title">Target OCVS ESXi Clusters and Workloads</text>
+  <g transform="translate(1098 596)">
+    <polygon class="host-base" points="0,42 92,42 76,82 16,82"/>
+    <rect class="host" x="0" y="16" width="92" height="26"/>
+    <text x="46" y="34" text-anchor="middle" font-family="Arial, sans-serif" font-size="12" font-weight="700" fill="#ffffff">ESXi</text>
+    <rect class="vm" x="8" y="0" width="18" height="14"/><rect class="vm" x="32" y="0" width="18" height="14"/><rect class="vm" x="56" y="0" width="18" height="14"/>
+  </g>
+  <g transform="translate(1244 596)">
+    <polygon class="host-base" points="0,42 92,42 76,82 16,82"/>
+    <rect class="host" x="0" y="16" width="92" height="26"/>
+    <text x="46" y="34" text-anchor="middle" font-family="Arial, sans-serif" font-size="12" font-weight="700" fill="#ffffff">ESXi</text>
+    <rect class="vm" x="8" y="0" width="18" height="14"/><rect class="vm" x="32" y="0" width="18" height="14"/><rect class="vm" x="56" y="0" width="18" height="14"/>
+  </g>
+  <g transform="translate(1390 596)">
+    <polygon class="host-base" points="0,42 92,42 76,82 16,82"/>
+    <rect class="host" x="0" y="16" width="92" height="26"/>
+    <text x="46" y="34" text-anchor="middle" font-family="Arial, sans-serif" font-size="12" font-weight="700" fill="#ffffff">ESXi</text>
+    <rect class="vm" x="8" y="0" width="18" height="14"/><rect class="vm" x="32" y="0" width="18" height="14"/><rect class="vm" x="56" y="0" width="18" height="14"/>
+  </g>
+
+  <path class="line-blue" marker-end="url(#arrow-blue)" d="M528 604 C650 570 950 570 1072 604"/>
+  <text x="800" y="560" text-anchor="middle" font-family="Arial, sans-serif" font-size="14" font-weight="700" fill="#0b5cab">Migration flows: vMotion, Bulk Migration, Replication Assisted vMotion</text>
+  <path class="line-green" marker-start="url(#arrow-green)" marker-end="url(#arrow-green)" d="M528 646 C650 690 950 690 1072 646"/>
+  <text x="800" y="714" text-anchor="middle" font-family="Arial, sans-serif" font-size="14" font-weight="700" fill="#15803d">Optional L2 Network Extension</text>
+
+</svg>