operations experience naming consistency

Author: asergaz

articles/iot-operations/connect-to-cloud/concept-schema-registry.md

@@ -99,7 +99,7 @@ Asset sources have a predefined message schema that was created by the connector
 
 Schemas can be uploaded for message broker sources. Currently, Azure IoT Operations supports JSON for source schemas, also known as input schemas. In the operations experience, you can select an existing schema or upload one while defining a message broker source:
 
-:::image type="content" source="./media/concept-schema-registry/upload-schema.png" alt-text="Screenshot that shows uploading a message schema in the operations experience portal.":::
+:::image type="content" source="./media/concept-schema-registry/upload-schema.png" alt-text="Screenshot that shows uploading a message schema in the operations experience web UI.":::
 
 ### Transformation
 
@@ -109,7 +109,7 @@ The operations experience uses the input schema as a starting point for your dat
 
 Output schemas are associated with data flow destinations.
 
-In the operations experience portal, you can configure output schemas for the following destination endpoints that support Parquet output:
+In the operations experience web UI, you can configure output schemas for the following destination endpoints that support Parquet output:
 
 * local storage
 * Fabric OneLake
@@ -126,7 +126,7 @@ To upload an output schema, see [Upload schema](#upload-schema).
 
 ## Upload schema
 
-Input schema can be uploaded in the operations experience portal as described in the [Input schema](#input-schema) section of this article. You can also upload a schema using the Azure CLI or a Bicep template. 
+Input schema can be uploaded in the operations experience web UI as described in the [Input schema](#input-schema) section of this article. You can also upload a schema using the Azure CLI or a Bicep template. 
 
 ### Upload schema with the CLI
 

articles/iot-operations/connect-to-cloud/howto-configure-adlsv2-endpoint.md

@@ -138,7 +138,7 @@ Then, create the *DataflowEndpoint* resource and specify the access token authen
 
 # [Portal](#tab/portal)
 
-See the [access token](#access-token) section for steps to create a secret in the operations experience portal.
+See the [access token](#access-token) section for steps to create a secret in the operations experience web UI.
 
 # [Bicep](#tab/bicep)
 
@@ -355,7 +355,7 @@ To enhance security and follow the principle of least privilege, you can generat
 # [Portal](#tab/portal)
 
 > [!IMPORTANT]
-> To use the operations experience portal to manage secrets, Azure IoT Operations must first be enabled with secure settings by configuring an Azure Key Vault and enabling workload identities. To learn more, see [Enable secure settings in Azure IoT Operations deployment](../deploy-iot-ops/howto-enable-secure-settings.md).
+> To use the operations experience web UI to manage secrets, Azure IoT Operations must first be enabled with secure settings by configuring an Azure Key Vault and enabling workload identities. To learn more, see [Enable secure settings in Azure IoT Operations deployment](../deploy-iot-ops/howto-enable-secure-settings.md).
 
 In the operations experience data flow endpoint settings page, select the **Basic** tab then choose **Authentication method** > **Access token**.
 

articles/iot-operations/connect-to-cloud/howto-configure-dataflow-profile.md

@@ -24,7 +24,7 @@ The most important setting is the instance count, which determines the number of
 By default, a data flow profile named *default* is created when Azure IoT Operations is deployed. This data flow profile has a single instance count. You can use this data flow profile to get started with Azure IoT Operations.
 
 > [!IMPORTANT]
-> Currently, the default data flow profile is the only profile supported by the [operations experience portal](https://iotoperations.azure.com/). All data flows created using the operations experience portal use the default data flow profile.
+> Currently, the default data flow profile is the only profile supported by the [operations experience web UI](https://iotoperations.azure.com/). All data flows created using the operations experience use the default data flow profile.
 
 # [Bicep](#tab/bicep)
 

articles/iot-operations/connect-to-cloud/howto-configure-fabric-real-time-intelligence.md

@@ -45,7 +45,7 @@ The connection string with the primary key.
 
 To configure a data flow endpoint for Microsoft Fabric Real-Time Intelligence, you need to use Simple Authentication and Security Layer (SASL) based authentication.
 
-Azure Key Vault is the recommended way to sync the connection string to the Kubernetes cluster so that it can be referenced in the data flow. [Secure settings](../deploy-iot-ops/howto-enable-secure-settings.md) must be enabled to configure this endpoint using the operations experience Portal.
+Azure Key Vault is the recommended way to sync the connection string to the Kubernetes cluster so that it can be referenced in the data flow. [Secure settings](../deploy-iot-ops/howto-enable-secure-settings.md) must be enabled to configure this endpoint using the operations experience web UI.
 
 # [Portal](#tab/portal)
 

articles/iot-operations/connect-to-cloud/howto-configure-kafka-endpoint.md

@@ -151,7 +151,7 @@ kubectl apply -f <FILE>.yaml
 # [Portal](#tab/portal)
 
 > [!IMPORTANT]
-> To use the operations experience portal to manage secrets, Azure IoT Operations must first be enabled with secure settings by configuring an Azure Key Vault and enabling workload identities. To learn more, see [Enable secure settings in Azure IoT Operations deployment](../deploy-iot-ops/howto-enable-secure-settings.md).
+> To use the operations experience web UI to manage secrets, Azure IoT Operations must first be enabled with secure settings by configuring an Azure Key Vault and enabling workload identities. To learn more, see [Enable secure settings in Azure IoT Operations deployment](../deploy-iot-ops/howto-enable-secure-settings.md).
 
 In the operations experience data flow endpoint settings page, select the **Basic** tab then choose **Authentication method** > **SASL**.
 

articles/iot-operations/connect-to-cloud/howto-configure-mqtt-endpoint.md

@@ -598,10 +598,10 @@ Before configuring the data flow endpoint, create a secret with the certificate
 # [Portal](#tab/portal)
 
 > [!IMPORTANT]
-> To use the operations experience portal to manage secrets, Azure IoT Operations must first be enabled with secure settings by configuring an Azure Key Vault and enabling workload identities. To learn more, see [Enable secure settings in Azure IoT Operations deployment](../deploy-iot-ops/howto-enable-secure-settings.md).
+> To use the operations experience web UI to manage secrets, Azure IoT Operations must first be enabled with secure settings by configuring an Azure Key Vault and enabling workload identities. To learn more, see [Enable secure settings in Azure IoT Operations deployment](../deploy-iot-ops/howto-enable-secure-settings.md).
 
 > [!IMPORTANT]
-> The operations experience portal currently has a known issue where creating an X.509 secret results in a secret with incorrectly encoded data. To learn more and the workaround, see [known issues](../troubleshoot/known-issues.md).
+> The operations experience web UI currently has a known issue where creating an X.509 secret results in a secret with incorrectly encoded data. To learn more and the workaround, see [known issues](../troubleshoot/known-issues.md).
 
 In the operations experience data flow endpoint settings page, select the **Basic** tab then choose **Authentication method** > **X509 certificate**.
 

articles/iot-operations/connect-to-cloud/howto-create-dataflow.md

@@ -16,7 +16,7 @@ ai-usage: ai-assisted
 
 [!INCLUDE [kubernetes-management-preview-note](../includes/kubernetes-management-preview-note.md)]
 
-A data flow is the path that data takes from the source to the destination with optional transformations. You can configure the data flow by creating a *Data flow* custom resource or using the Azure IoT Operations Studio portal. A data flow is made up of three parts: the **source**, the **transformation**, and the **destination**. 
+A data flow is the path that data takes from the source to the destination with optional transformations. You can configure the data flow by creating a *Data flow* custom resource or using the operations experience web UI. A data flow is made up of three parts: the **source**, the **transformation**, and the **destination**. 
 
 <!--
 ```mermaid
@@ -447,7 +447,7 @@ sourceSettings:
 
 ### Specify source schema
 
-When using MQTT or Kafka as the source, you can specify a [schema](concept-schema-registry.md) to display the list of data points in the operations experience portal. Using a schema to deserialize and validate incoming messages [isn't currently supported](../troubleshoot/known-issues.md#data-flows).
+When using MQTT or Kafka as the source, you can specify a [schema](concept-schema-registry.md) to display the list of data points in the operations experience web UI. Using a schema to deserialize and validate incoming messages [isn't currently supported](../troubleshoot/known-issues.md#data-flows).
 
 If the source is an asset, the schema is automatically inferred from the asset definition.
 

articles/iot-operations/end-to-end-tutorials/tutorial-upload-telemetry-to-cloud.md

@@ -98,15 +98,15 @@ az role assignment create --role "Azure Event Hubs Data Sender" --assignee $PRIN
 
 ## Create a data flow to send telemetry to an event hub
 
-Use the operations experience UI to create and configure a data flow in your cluster that:
+Use the operations experience web UI to create and configure a data flow in your cluster that:
 
 - Renames the `temperature` field in the incoming message to `TemperatureF`.
 - Adds a field called `AssetId` that contains the name of the asset.
 - Forwards the transformed messages from the MQTT topic to the event hub you created.
 
 To create the data flow:
 
-1. Browse to the operations experience UI and locate your instance. Then select **Data flow endpoints** and select **+ New** in the **Azure Event Hubs** tile:
+1. Browse to the operations experience web UI and locate your instance. Then select **Data flow endpoints** and select **+ New** in the **Azure Event Hubs** tile:
 
     :::image type="content" source="media/tutorial-upload-telemetry-to-cloud/new-event-hubs-endpoint.png" alt-text="Screenshot of the data flow endpoints page.":::
 

articles/iot-operations/secure-iot-ops/howto-manage-secrets.md

@@ -50,6 +50,6 @@ You can use **Manage secrets** for asset endpoints and data flow endpoints to ma
 You can delete synced secrets as well in manage secrets. When you delete a synced secret, it only deletes the synced secret from the edge, and doesn't delete the contained secret reference from key vault. 
 
 > [!WARNING]
-> Directly editing **SecretProviderClass** and **SecretSync** custom resources in your Kubernetes cluster can break the secrets flow in Azure IoT Operations. For any operations related to secrets, use the operations experience UI.
+> Directly editing **SecretProviderClass** and **SecretSync** custom resources in your Kubernetes cluster can break the secrets flow in Azure IoT Operations. For any operations related to secrets, use the operations experience web UI.
 >
 > Before deleting a synced secret, make sure that all references to the secret from Azure IoT Operations components are removed.

articles/iot-operations/troubleshoot/known-issues.md

@@ -111,14 +111,14 @@ kubectl delete pod aio-opc-opc.tcp-1-f95d76c54-w9v9c -n azure-iot-operations
 
 ## Data flows
 
-- Data flow custom resources created in your cluster aren't visible in the operations experience UI. This is expected because [managing Azure IoT Operations components using Kubernetes is in preview](../deploy-iot-ops/howto-manage-update-uninstall.md#preview-manage-components-using-kubernetes-deployment-manifests), and synchronizing resources from the edge to the cloud isn't currently supported.
+- Data flow custom resources created in your cluster aren't visible in the operations experience web UI. This is expected because [managing Azure IoT Operations components using Kubernetes is in preview](../deploy-iot-ops/howto-manage-update-uninstall.md#preview-manage-components-using-kubernetes-deployment-manifests), and synchronizing resources from the edge to the cloud isn't currently supported.
 
 - X.509 authentication for custom Kafka endpoints isn't supported yet.
 
-- Deserializing and validating messages using a schema isn't supported yet. Specifying a schema in the source configuration only allows the operations experience portal to display the list of data points, but the data points aren't validated against the schema.
+- Deserializing and validating messages using a schema isn't supported yet. Specifying a schema in the source configuration only allows the operations experience to display the list of data points, but the data points aren't validated against the schema.
 
 <!-- TODO: double check -->
-- Creating an X.509 secret in the operations experience portal results in a secret with incorrectly encoded data. To work around this issue, create the [multi-line secrets through Azure Key Vault](/azure/key-vault/secrets/multiline-secrets), then select it from the list of secrets in the operations experience portal.
+- Creating an X.509 secret in the operations experience results in a secret with incorrectly encoded data. To work around this issue, create the [multi-line secrets through Azure Key Vault](/azure/key-vault/secrets/multiline-secrets), then select it from the list of secrets in the operations experience.
 
 - When connecting multiple IoT Operations instances to the same Event Grid MQTT namespace, connection failures may occur due to client ID conflicts. Client IDs are currently derived from data flow resource names, and when using Infrastructure as Code (IaC) patterns for deployment, the generated client IDs may be identical. As a temporary workaround, add randomness to the data flow names in your deployment templates.