Fix minor bugs in the docs

Author: VidyaKukke

articles/event-grid/edge/monitor-topics-subscriptions.md

@@ -35,7 +35,7 @@ Configure the module to emit metrics by setting the `metrics__reporterType` envi
         }
  ```    
 
-Metrics will be available at `5888/metrics` of the module for http and `4438/metrics` for https. For example, `http://<modulename>:4438/metrics?api-version=2019-01-01-preview` for http. At this point, a metrics module can poll the endpoint to collect metrics as in this [example architecture](https://github.com/veyalla/ehm).
+Metrics will be available at `5888/metrics` of the module for http and `4438/metrics` for https. For example, `http://<modulename>:5888/metrics?api-version=2019-01-01-preview` for http. At this point, a metrics module can poll the endpoint to collect metrics as in this [example architecture](https://github.com/veyalla/ehm).
 
 ## Available metrics
 

articles/event-grid/edge/persist-state-linux.md

@@ -111,7 +111,8 @@ Instead of a docker volume, you also have the option to mount a host folder.
     {
          "HostConfig": {
             "Binds": [
-                "<your-directory-name-here>:/app/metadataDb"
+                "<your-directory-name-here>:/app/metadataDb",
+                "<your-directory-name-here>:/app/eventsDb",
              ]
          }
     }
@@ -151,7 +152,7 @@ Instead of a docker volume, you also have the option to mount a host folder.
     ```
 
     >[!IMPORTANT]
-    >Do not change the second part of the bind value. It points to a specific location within the module. For the Event Grid module on linux, it has to be **/app/metadata**.
+    >Do not change the second part of the bind value. It points to a specific location within the module. For the Event Grid module on linux, it has to be **/app/metadataDb** and **/app/eventsDb**
 
 
 ## Persist events

articles/event-grid/edge/persist-state-windows.md

@@ -207,13 +207,13 @@ Instead of mounting a volume, you can create a directory on the host system and
     ```
 ## Persist events
 
-To enable event persistence, you must first enable metadata persistence either via volume mount or host directory mount using the above sections.
+To enable event persistence, you must first enable events persistence either via volume mount or host directory mount using the above sections.
 
 Important things to note about persisting events:
 
 * Persisting events is enabled on a per Event Subscription basis and is opt-in once a volume or directory has been mounted.
 * Event persistence is configured on an Event Subscription at creation time and cannot be modified once the Event Subscription is created. To toggle event persistence, you must delete and re-create the Event Subscription.
-* Persisting events is almost always slower than in memory operations, however the speed difference is highly dependent on the characteristics of the drive. The tradeoff between speed and reliability is inherent to all messaging systems but only becomes a noticible at large scale.
+* Persisting events is almost always slower than in memory operations, however the speed difference is highly dependent on the characteristics of the drive. The tradeoff between speed and reliability is inherent to all messaging systems but only becomes a noticeable at large scale.
 
 To enable event persistence on an Event Subscription, set `persistencePolicy` to `true`: