docs: restructuring Interaction section in User Guide

docs/user-guide/Configuration.md

@@ -46,8 +46,8 @@ example of how to separate service code from configuration.
   port. Default: `8001`.
 
 - **`GENERATE_WEB_SETTINGS`**:  
-  When `true`, generates or updates the `web_settings.json` file (see [Tailoring Frontend Component Layout](../interaction/#tailoring-frontend-component-layout)). Existing entries are
-  preserved, and new entries are appended.
+  When `true`, generates or updates the `web_settings.json` file (see [Tailoring Frontend Component Layout](./interaction/Auto-generated-Frontend.md#tailoring-frontend-component-layout)).
+  Existing entries are preserved, and new entries are appended.
 
 ### Configuring `pydase` via Keyword Arguments
 

docs/user-guide/interaction/README.md

@@ -1,18 +1,7 @@
 # Interacting with `pydase` Services
 
-`pydase` offers multiple ways for users to interact with the services they create, providing flexibility and convenience for different use cases. This section outlines the primary interaction methods available, including an auto-generated frontend, a RESTful API, and a Python client based on Socket.IO.
+`pydase` offers multiple ways for users to interact with the services they create.
 
-{%
-   include-markdown "./Auto-generated Frontend.md"
-   heading-offset=1
-%}
-
-{%
-   include-markdown "./RESTful API.md"
-   heading-offset=1
-%}
-
-{%
-   include-markdown "./Python Client.md"
-   heading-offset=1
-%}
+- [Auto-generated Frontend](./Auto-generated-Frontend.md)
+- [RESTful API](./RESTful-API.md)
+- [Python Client](./Python-Client.md)