Changed SIDB readme

Author: mmahipal

docs/sidb/README.md

@@ -8,7 +8,6 @@ Oracle Database Operator for Kubernetes (the operator) includes the Single Insta
 * [Clone Existing Database](#clone-existing-database)
 * [Patch/Rollback Database](#patchrollback-database)
 
-
 ## Prerequisites
 
 Oracle strongly recommends that you follow the [Prerequisites](./SIDB_PREREQUISITES.md).
@@ -233,18 +232,17 @@ $ kubectl get singleinstancedatabase sidb-sample -o "jsonpath={.status.status}"
 
 ## Patch/Rollback Database
 
-  Databases running in your cluster and managed by this operator can be patched or rolled back between release updates of the same major release. To patch databases, specify an image of the higher release update, and to roll back, specify an image of the lower release update. 
+  Databases running in your cluster and managed by this operator can be patched or rolled back between release updates of the same major release. To patch databases, specify an image of the higher release update, and to roll back, specify an image of the lower release update.
 
   Patched Oracle Docker images can be built using this [patching extension](https://github.com/oracle/docker-images/tree/main/OracleDatabase/SingleInstance/extensions/patching)
 
-* ### Patching
+* ### Patch the Database
 
-  Edit the `singleinstancedatabase.yaml` file of the database resource/object and specify a new release update for release or image attributes and apply the `singleinstancedatabase.yaml` file. The database pods will be restarted with the new release update image. For minimum downtime, ensure that you have mutiple replicas of the database pods running.
+  Edit and apply the `singleinstancedatabase.yaml` file of the database resource/object by specifying a new release update for image attributes. The database pods will be restarted with the new release update image. For minimum downtime, ensure that you have mutiple replicas of the database pods running.
 
-* ### Clone and Patch
+* ### Clone and Patch the Database
 
-  Clone your source database using the method of [cloning existing database](README.md#clone-existing-database) and specify a new release version/image for the
-  cloned database. Use this method to enusure there are no patching related issues impacting your database performance/functionality
+  Clone your source database using the method of [cloning existing database](README.md#clone-existing-database) and specify a new release image for the cloned database. Use this method to enusure there are no patching related issues impacting your database performance/functionality
 
 * ### Datapatch status