Updated corresponding PR review

Author: dimamost

java/operating-applications/dashboard.md

@@ -2,7 +2,6 @@
 synopsis: >
   This section describes how the CAP Developer Dashboard can be set up in both the local and cloud development environment to improve the developer experience.
 status: released
-redirect_from: java/observability
 ---
 
 # Developer Dashboard
@@ -24,6 +23,8 @@ The dashboard is only intended for use in the development environment. It is str
 
 The CAP Developer Dashboard simplifies development by providing a centralized point where developers can efficiently manage and monitor their CAP applications. It offers tools and functions to support the development process and helps developers to quickly identify and resolve problems. Additionally, the dashboard facilitates better integration of CAP components, such as messaging, resilience and multitenancy, ensuring seamless functionality throughout CAP applications.
 
+You can get a brief overview of the dashboard's features in the [Developer Dashboard Presentation](https://broadcast.sap.com/replay/240604_recap?playhead=2188) at our RECAP 2024 conference.
+
 Add the `cds-feature-dev-dashboard` feature to your maven dependencies:
 
 ```xml [pom.xml]
@@ -54,25 +55,35 @@ cds:
 
 If you also want to use the CAP Developer Dashboard in your cloud development scenario, you need to take a few more steps to achieve this. Let's take an example of a BTP Cloud Foundry app example with Approuter and XSUAA.
 
-First you must deactivate the [production profile](https://pages.github.tools.sap/cap/docs/java/developing-applications/configuring#production-profile). To do this, set the property `cds.environment.production.enabled` in `application.yaml` or `CDS_ENVIRONMENT_PRODUCTION_ENABLED` in `mta.yaml` to `false`.
+- First you must deactivate the [production profile](https://pages.github.tools.sap/cap/docs/java/developing-applications/configuring#production-profile). To do this, set the property `cds.environment.production.enabled` in **application.yaml** or `CDS_ENVIRONMENT_PRODUCTION_ENABLED` in **mta.yaml** to `false`.
+
+- Second, you need to add the `cds.Developer` role to your security configuration (**xs-security.json** is an example of the XSUAA configuration).
 
-Second, you need to add the `cds.Developer` role to your security configuration. Here is an example of the XSUAA configuration:
+- And finally, you need to customize the approuter configuration (**xs-app.json**) by enabling support for websocket connections and defining the dashboard routes.
 
 ::: code-group
+```yaml [mta.yaml]
+modules:
+  - name: my-cap-app-srv
+    [...]
+    properties:
+      CDS_ENVIRONMENT_PRODUCTION_ENABLED: false
+```
+
 ```json [xs-security.json]
 {
 	"xsappname": "dashboard-test",
-	...
+	[...]
 	"scopes": [
 		{
 			"name": "$XSAPPNAME.cds.Developer",
 			"description": "CAP Developer"
 		},
-    ...
+    [...]
 	],
  "attributes": [
 		{
-			...
+			[...]
 		}
 	],
 	"role-templates": [
@@ -83,15 +94,11 @@ Second, you need to add the `cds.Developer` role to your security configuration.
 				"$XSAPPNAME.cds.Developer"
 			]
 		},
-    ...
+    [...]
 	]
 }
 ```
-:::
 
-Finally, you need to customize the approuter configuration by enabling support for websocket connections and defining the dashboard routes:
-
-::: code-group
 ```json [xs-app.json]
 {
 	...
@@ -115,7 +122,7 @@ Finally, you need to customize the approuter configuration by enabling support f
 			"authenticationType": "xsuaa",
 			"destination": "backend"
 		}, 
-    ...
+    [...]
 	]
 }
 ```
@@ -127,9 +134,9 @@ Now you can deploy the application in BTP and assign the `cds.Developer` role to
 For security reasons, the **cds.Developer** role should only be used in conjunction with test users. It is strongly recommended not to use this role with users who could potentially be used in production systems.
 :::
 
-## Unauthorized Access
+## Disable Authorization
 
-In some cases, your application may run in a complex environment such as DwC and you simply want to access the CAP Developer Dashboard running in your CAP Service Module directly without using a router in between. For this reason, you can switch off the authorization to grant direct unauthorized access. 
+In some cases, your application may run in a complex environment such as DwC and you simply want to access the CAP Developer Dashboard running in your CAP Service Module directly without using a router in between. For this reason, you can switch off the authorization to grant direct unauthorized access (either via the static configuration **application.yaml** or in the deployment configuration **mta.yaml**). 
 
 ::: code-group
 ```yaml [application.yaml]
@@ -138,6 +145,15 @@ cds:
     authorization:
       enabled: false
 ```
+
+```yaml [mta.yaml]
+modules:
+  - name: my-cap-app-srv
+    [...]
+    properties:
+      CDS_DASHBOARD_AUTHORIZATION_ENABLED: false
+```
+
 :::
 
 To open finally the endpoint, authentication can be disabled via the spring web security configuration. Alternatively, the DwC web security configuration is provided to disable mTLS for the CAP Developer Dashboard endpoint.