update language

Author: mdbirnstiehl

solutions/observability/streams/management/advanced.md

@@ -27,10 +27,10 @@ Features provide useful information for AI processes, such as significant events
 ## Index configuration [streams-advanced-index-config]
 
 :::{Important}
-Avoid editing assets marked as *managed* or any per-data-stream mappings and settings. Processing and schema changes should typically be done through the Streams interface or API, and none of these configuration processes are required. This feature mainly exists to help advanced users maintain familiar workflows.
+Avoid editing components marked as **managed** or any per-data-stream mappings and settings. Processing and schema changes should typically be done through the Streams interface or API, and none of these configuration processes are required. This feature mainly exists to help advanced users maintain familiar workflows.
 :::
 
-For classic streams, you can access the following assets:
+For classic streams, you can access the following components:
 
 - [Index templates](../../../../manage-data/data-store/templates.md#index-templates)
 - [Component templates](../../../../manage-data/data-store/templates.md#component-templates)

solutions/observability/streams/streams.md

@@ -37,10 +37,10 @@ Wired streams:
 
 For more information, refer to [sending data to wired streams](./wired-streams.md).
 
-## Managed assets
-When you configure classic or wired streams through the Streams UI or [Streams API](#streams-api), {{es}}-level assets like templates and pipelines are created for the stream. These assets are considered *managed* and shouldn't be modified using {{es}} APIs. When managing a stream through the Streams UI or API, continue doing so whenever possible.
+## Managed components
+When you configure classic or wired streams through the Streams UI or [Streams API](#streams-api), {{es}}-level components like templates and pipelines are created for the stream. These components are considered *managed* and shouldn't be modified using {{es}} APIs. When managing a stream through the Streams UI or API, continue doing so whenever possible.
 
-You can still edit non-managed ingest pipelines, templates, and other assets, but avoid editing assets marked as managed or any per-data-stream mappings and settings. This behavior is similar to how Elasticsearch handles assets managed by integrations. Refer to the [advanced tab](./management/advanced.md) to review managed assets.
+You can still edit non-managed ingest pipelines, templates, and other components, but avoid those marked as managed or any per-data-stream mappings and settings. This behavior is similar to how Elasticsearch handles components managed by integrations. Refer to the [advanced tab](./management/advanced.md) to review managed components.
 
 ## Required permissions