Update README.md

formatting and typo

Author: AlexanderHodicke

data-platform/mission-critical-database/Disaster Recovery/README.md

@@ -1,16 +1,16 @@
 # Disaster Recovery
-Deals with the technologies supporting disaster recovery, specifically Dataguard, but also covering services such as FSDR (Full Stack Disaster Recovery)
 
-Oracle Data Guard or Active Data Guard is the most effective solution to protect data of any enterprise and make it available on a 24x7 basis in the face of disasters and other calamities. Data Guard or Active Data Guard is essential for Mission Critical for Enterprise Database. Data Guard Cloud functionality includes MAA configuration, Data Guard role transitions and Monitoring.
-A database disaster is an event that causes DATA LOSS or SERIOUS DISRUPTION to applications and services. There can be various causes: power failure, hardware failure, cyber-attacks, natural disasters, fire, earthquakes, vandalism, human error, planned maintenance, etc. Most of the database server disasters cannot be prevented. Disaster Recovery provides SERVICE CONTINUITY in case of any geographical disasters or by planned outages by recovering or resuming the services from a geographically different location. This page will help you get started to understand some basic requirements for Disaster Recovery Opportunities with Data Guard/Active Data Guard.
+It deals with the technologies supporting disaster recovery, specifically Dataguard, but also covers services such as FSDR (Full Stack Disaster Recovery)
 
-# Useful Links
+Oracle Data Guard or Active Data Guard is the most effective solution to protect the data of any enterprise and make it available on a 24x7 basis in the face of disasters and other calamities. Data Guard or Active Data Guard is essential for Mission Critical Enterprise Database. Data Guard Cloud functionality includes MAA configuration, Data Guard role transitions, and Monitoring.
+A database disaster is an event that causes DATA LOSS or SERIOUS DISRUPTION to applications and services. There can be various causes: power failure, hardware failure, cyber-attacks, natural disasters, fire, earthquakes, vandalism, human error, planned maintenance, etc. Most database server disasters cannot be prevented. Disaster Recovery provides SERVICE CONTINUITY in case of geographical disasters or planned outages by recovering or resuming services from a geographically different location. This page will help you get started to understand some basic requirements for Disaster Recovery Opportunities with Data Guard/Active Data Guard.
 
- FAQs for Data Guard (Doc ID 2930929.1) (Login to MOS and search for Doc)
-Disaster Recovery: https://www.oracle.com/cloud/backup-and-disaster-recovery/what-is-disaster-recovery/#cloud-based-deployment
-Data Guard Best Practices: https://docs.oracle.com/en/database/oracle/oracle-database/19/haovw/oracle-data-guard-best-practices.html
+# Useful Links
 
-Introduction to Full Stack Disaster Recovery: https://www.youtube.com/watch?v=GiyFs8Cpksg&t=587s
+- FAQs for Data Guard (Doc ID 2930929.1) (Log in to MOS and search for Doc)
+- [Disaster Recovery](https://www.oracle.com/cloud/backup-and-disaster-recovery/what-is-disaster-recovery/#cloud-based-deployment)
+- [Data Guard Best Practices](https://docs.oracle.com/en/database/oracle/oracle-database/19/haovw/oracle-data-guard-best-practices.html)
+- [Introduction to Full Stack Disaster Recovery](https://www.youtube.com/watch?v=GiyFs8Cpksg&t=587s)
 
 # License