Correction in Readme

api/README.md

@@ -234,7 +234,7 @@ PREvant calls this function with the app name (see `appName`) and an array of se
 | `files`       | A map of key and value containing the files that will be mounted into the container.                       |
 
 ## Persistence Hooks
-Persistence Hooks in PREvant are designed to handle data persistence by managing volume paths of services. For example, you can use a Persistence Hook to dynamically adjust persistence paths for data backups. Based on the 
+Persistence Hooks in PREvant are designed to handle data persistence by managing volume paths of services. For example, you can use a Persistence Hook to configure any services that share a persistence path or add missing additional paths that caters to unreleased features.
 
 Like Deployment Hooks, these hooks are Javascript files that provide functions to manage and manipulate persistence settings. This configuration snippet enables the _persistence hook_ that will be used to modify the services' configurations.
 
@@ -250,7 +250,7 @@ function persistenceHook(appName, serviceConfigs) {
   //Return Array of an Array of pairs of service name and path.
 }
 ```
-Note: The input to thePersistence Hook is an array of name and path pairs. If multiple paths are declared in the configuration, they are split and treated as separate pairs.
+Note: The input to the Persistence Hook is an array of name and path pairs. If multiple paths are declared in the configuration, they are split and treated as separate pairs.
 
 PREvant will invoke this function with an array of service config with name and path as fields. This input can be modified according to the required persistence logic and must be returned by the function in an Array of Arrays format. The output structure allows for grouping shared paths or treating them as individual, based on the deployment's specific requirements.