Remove APM UI, RUM source map, and managed intake service API pages

solutions/observability/apps/apm-ui-api.md

@@ -12,7 +12,7 @@ Some Applications UI features are provided via a REST API:
 
 * Agent Configuration API ([{{stack}}](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-apm-agent-configuration) or [{{serverless-short}}](https://www.elastic.co/docs/api/doc/serverless/group/endpoint-apm-agent-configuration))
 * Annotation API ([{{stack}}](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-apm-annotations) or [{{serverless-short}}](https://www.elastic.co/docs/api/doc/serverless/group/endpoint-apm-annotations))
-* [RUM source map API](rum-source-map-api.md)
+* RUM source map API ([{{stack}}](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-apm-sourcemaps) or [{{serverless-short}}](https://www.elastic.co/docs/api/doc/serverless/group/endpoint-apm-sourcemaps))
 * APM agent key API ([{{stack}}](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-apm-agent-keys) or [{{serverless-short}}](https://www.elastic.co/docs/api/doc/serverless/group/endpoint-apm-agent-keys))
 
 

solutions/observability/apps/create-assign-feature-roles-to-apm-server-users.md

@@ -262,4 +262,4 @@ Assign additional APM feature roles to users as needed including the [*Writer ro
 ::::
 
 
-The previous privileges should be sufficient for RUM source mapping to work properly as long as APM Server communicates with {{es}} successfully. If it fails, it may fallback to read source maps through {{kib}} if configured, which requires additional {{kib}} privileges. See [RUM source map API](rum-source-map-api.md) for more details.
+The previous privileges should be sufficient for RUM source mapping to work properly as long as APM Server communicates with {{es}} successfully. If it fails, it may fallback to read source maps through {{kib}} if configured, which requires additional {{kib}} privileges. For more details, refer to the [{{stack}}](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-apm-sourcemaps) or [{{serverless-short}}](https://www.elastic.co/docs/api/doc/serverless/group/endpoint-apm-sourcemaps) API documentation.

solutions/observability/apps/create-upload-source-maps-rum.md

@@ -91,7 +91,7 @@ When uploading a source map, ensure that RUM support is enabled in the APM integ
 ::::
 
 
-{{kib}} exposes a [source map endpoint](rum-source-map-api.md) for uploading source maps. Source maps can be uploaded as a string, or as a file upload.
+{{kib}} exposes a source map endpoint for uploading source maps. Source maps can be uploaded as a string, or as a file upload.
 
 Let’s look at two different ways to upload a source map: curl and a custom application. Each example includes the four fields necessary for APM Server to later map minified code to its source:
 
@@ -120,9 +120,7 @@ curl -X POST "http://localhost:5601/api/apm/sourcemaps" \
 ```
 
 1. This example uses the version from `package.json`
-2. The API key used here needs to have appropriate [privileges](rum-source-map-api.md)
-
-
+2. The API key used here needs to have appropriate privileges. Refer to the [{{stack}}](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-apm-sourcemaps) or [{{serverless-short}}](https://www.elastic.co/docs/api/doc/serverless/group/endpoint-apm-sourcemaps) API documentation.
 
 ### Upload via a custom app [apm-source-map-custom-app]
 

solutions/toc.yml

@@ -165,7 +165,6 @@ toc:
                 children:
                   - file: observability/apps/apm-ui-api.md
                     children:
-                      - file: observability/apps/rum-source-map-api.md
                       - file: observability/apps/managed-intake-service-event-api.md
                   - file: observability/apps/apm-server-api.md
                     children: