diff --git a/gatsby-config.js b/gatsby-config.js
index 7ce2e978..e01e4c0f 100644
--- a/gatsby-config.js
+++ b/gatsby-config.js
@@ -244,7 +244,7 @@ module.exports = {
             path: "/services/aem-universal-editor/api/item-types-renderers/"
           },
           {
-            title: "Supported events",
+            title: "Working with events",
             path: "/services/aem-universal-editor/api/events/"
           },
           {
diff --git a/src/pages/services/aem-universal-editor/api/commons/index.md b/src/pages/services/aem-universal-editor/api/commons/index.md
index 3323fdc1..ab385631 100644
--- a/src/pages/services/aem-universal-editor/api/commons/index.md
+++ b/src/pages/services/aem-universal-editor/api/commons/index.md
@@ -47,9 +47,9 @@ Editor and extension and needed if extension provides custom UI.
 - `methods` - objects with extension code exposed to the Universal Editor console. All methods are grouped into 
 namespaces that represents extension points provided by the Universal Editor.
 Currently, the following **namespaces** are available:
-- _headerMenu_, that allows to add buttons to the header of the Universal Editor;
-- _rightPanel_, that allows to add custom content under the rails to the right panel of the Universal Editor;
-- _canvas_, that allows to add custom renderer for data types
+  - _headerMenu_, that allows to add buttons to the header of the Universal Editor;
+  - _rightPanel_, that allows to add custom content under the rails to the right panel of the Universal Editor;
+  - _canvas_, that allows to add custom renderer for data types
 
 ```js
 import { register } from "@adobe/uix-guest";
diff --git a/src/pages/services/aem-universal-editor/api/events/index.md b/src/pages/services/aem-universal-editor/api/events/index.md
index d064e857..950c3dfc 100644
--- a/src/pages/services/aem-universal-editor/api/events/index.md
+++ b/src/pages/services/aem-universal-editor/api/events/index.md
@@ -7,7 +7,7 @@ contributors:
 
 # Working with Events
 
-the Universal Editor sends defined events to remote applications. In case the remote application has no custom event listener for the sent event, a fallback event listener provided by the universal-editor-cors package is executed.
+The Universal Editor sends defined events to remote applications. In case the remote application has no custom event listener for the sent event, a fallback event listener provided by the universal-editor-cors package is executed.
 
 ### Working with Events
 
@@ -29,7 +29,7 @@ For instance, here's an example of how to subscribe to the "aue:ui-select" event
 ```
 
 If your business logic requires sending an event to the Universal Editor, you can use the `dispatchEvent` method.
-Here's an example of how to dispatch the "aue:ui-select" event:
+Here's an example of how to dispatch the `aue:ui-select` event:
 
 ```js
     useEffect(() => {
diff --git a/src/pages/services/aem-universal-editor/api/properties-rails/index.md b/src/pages/services/aem-universal-editor/api/properties-rails/index.md
index 8fe92283..4fa5749a 100644
--- a/src/pages/services/aem-universal-editor/api/properties-rails/index.md
+++ b/src/pages/services/aem-universal-editor/api/properties-rails/index.md
@@ -104,7 +104,7 @@ export default () => {
     }
 
     // If you need to interact with an AEM instance
-    // const connection = await attach({ id: extensionId });
+     const connection = await attach({ id: extensionId });
 
     return (
         <Provider theme={lightTheme} colorScheme="light">
@@ -159,4 +159,4 @@ Examples: `ctrl+k`, `ctrl+shift+s`, `shift+arrowup`, `c.`
 
 ## Limitation
 
-Each click on the icon corresponding to the panel will result in the re-rendering of that panel. The panel content is not cached and will be re-ren
+Each click on the icon corresponding to the panel will result in the re-rendering of that panel. The panel content is not cached and will be re-rendered