added text to complexity section in overview

Author: gvasquezvargas

advocacy_docs/migrating/oracle/workaround_overview.mdx

@@ -4,24 +4,44 @@ description: "Workaround overview"
 indexCards: none
 ---
 
-EBD offers several solutions for the sucessful migration of Oracle databases to Postgres. This guide offers practical aids, such as a collection of features (functions, views, queries, etc.) commonly used in Oracle accompanied by examples on how to adapt them to Postgres.
+EDB provides a version of Postgres that is compatible with most of the built-in Oracle features. This greatly simplifies migrations from Oracle by allowing many objects and application queries to work in Postgres without having to modify them. 
+Additionally, EBD offers several migration tools (Migration Portal, AI Copilot, Migration Toolkit, Replication Server) that facilitate the migration of complex Oracle databases to EDB Postgres. 
 
-If you are migrating to EDB Postgres Advanced Server, the Migration Portal and the AI Copilot may have already helped you convert most schemas. This section offers further reference material for the schemas that were not converted automatically. 
+For the remaining incompatibilities, EDB offers this workaround guide with practical aids for features and issues that could not be resolved automatically. It presents a collection of manual solutions to convert features and queries accompanied by examples on how to address them.
 
-If you are migrating to PostgreSQL or EDB Postgres Extended Server, this section offers reference material for you to convert schemas manually.
+Each workaround displays a table that contains a summary of the solution's most important things to consider. 
 
-## Layout 
+## Solution complexity 
 
-Each workaround contains the following sections: 
+Specifies the complexity and level of effort to address the issue.
 
-- Solution summary: a short overview of the solutions' complexity, availability and type. 
-- Feature in Oracle: explains how the feature is used in Oracle with an example. 
-- PostgreSQL solution: provides an example of how to adapt the function to PostgreSQL and EDB Postgres Extended Server. 
-- EDB Postgres Advanced Server solution: provides an example of how to adapt the function to EDB Postgres Advanced Server.
-- Migration considerations: provides further information to take into account when adapting the function. 
+- **Easy:** 
+  These workarounds require minimal effort and are easy to implement. The compatibility with EDB Postgres is very high and the solution involves simple modifications. Performing tests to validate the solution is recommended.
 
-## Complexity 
+- **Moderate:** 
+  These issues are still easily manageable and don't require a lot of backgroung knowledge. The compatibility with EDB Postgres is high and the solution involves modifications. Performing tests to validate the solution is recommended.
+
+- **Intermediate:** 
+  The solution may require an understanding of the Oracle database. You may need to perform troubleshooting efforts and performing comprehensive tests to validate the solution is recommended.
+
+- **Significant:** 
+  Finding an equivalent for these functions requires effort, planning and a deeper understanding of Oracle and Postgres databases. The solution may involve extensive modifications like using a combination of functions to reflect the original function. You will need to perform comprehensive troubleshooting efforts and end-to-end testing to validate the equivalent. 
+
+- **Difficult:** 
+  Finding an equivalent for these functions requires effort, planning and a deeper understanding of Oracle and Postgres databases. The solution will involve extensive modifications like using a combination of functions to reflect the original function. You will need to perform comprehensive troubleshooting efforts and end-to-end testing to validate the equivalent. 
+   
 
 ## Availability 
 
-## Type 
+Specifies the EDB Postgres distributions where the solution is available.
+
+- Yes, fully convertible to EDB Postgres and EDB Postgres Advanced Server
+- No, partially convertible or no available equivalent. 
+
+[Are there possibly solutions that will only apply to EPAS and not to PG? Do we need a category for that?]#
+
+## Type 
+
+- In Database 
+- MP Repair Handler
+- Other