Address feedback

dominicbetts · dominicbetts · commit 560377d017c5 · 2024-11-14T10:57:34.000Z
diff --git a/articles/iot-operations/discover-manage-assets/howto-use-media-connector.md b/articles/iot-operations/discover-manage-assets/howto-use-media-connector.md
@@ -141,19 +141,19 @@ These parameters configure:
 
 The default MQTT topic name that the connector publishes to is `<connector namespace>/data/<asset name>`.
 
-To apply the previous configuration, save the examples above as files, and run the following command:
+To apply the previous configuration, save the previous examples as files, and run the following command:
 
 ```azurecli
 az deployment group create --resource-group <your resource group> --template-file aep-camera-anonymous.bicep --parameters snapshot-to-mqtt-autostart.json --parameters customLocationName=<your custom location>
 ```
 
 [!INCLUDE [discover-custom-location](../includes/discover-custom-location.md)]
 
-This asset configuration publishes snapshots from the video stream to an MQTT topic. To view the snapshots, you can subscribe to the MQTT topic. To learn more about how to subscribe to an MQTT topic in a non-production environment, see [Test connectivity to MQTT broker with MQTT clients](../manage-mqtt-broker/howto-test-connection.md).
+This asset configuration publishes snapshots from the video stream to an MQTT topic. To view the snapshots, you can subscribe to the MQTT topic. To learn more about how to subscribe to an MQTT topic in a nonproduction environment, see [Test connectivity to MQTT broker with MQTT clients](../manage-mqtt-broker/howto-test-connection.md).
 
 ## Dataset configuration
 
-The `datasetsDataPoints` parameter specifies the action the the media connector takes on the asset. The previous example configures the camera to capture snapshots to publish to an MQTT broker topic. A camera asset supports the following five task types:
+The `datasetsDataPoints` parameter specifies the action the media connector takes on the asset. The previous example configures the camera to capture snapshots to publish to an MQTT broker topic. A camera asset supports the following five task types:
 
 | Task type | Description |
 |-----------|-------------|
diff --git a/articles/iot-operations/discover-manage-assets/howto-use-onvif-connector.md b/articles/iot-operations/discover-manage-assets/howto-use-onvif-connector.md
@@ -156,7 +156,7 @@ The following JSON snippet shows a set of parameter values to use:
 
 These parameters configure:
 
-- The name of the asset to create.
+- The name of the asset to create. The `-ptz` suffix is a reuired convention to indicate that the asset represents the PTZ capabilities of the camera.
 - The associated asset endpoint you created previously.
 
 To apply the previous configuration, save the examples above as files, and run the following command:
diff --git a/articles/iot-operations/discover-manage-assets/overview-media-connector.md b/articles/iot-operations/discover-manage-assets/overview-media-connector.md
@@ -12,19 +12,19 @@ ms.date: 11/12/2024
 
 # What is the Azure IoT Operations media connector (preview)?
 
-This article introduces the media connector (preview) in Azure IoT Operations. The media connector makes images and video from media sources such as edge attached cameras available to other Azure IoT Operations components. The media connector is secure and performant.
+This article introduces the media connector (preview) in Azure IoT Operations. The media connector makes images and video from media sources such as IP cameras available to other Azure IoT Operations components. The media connector is secure and performant.
 
 ## Media source types
 
-The media connector can connect to a variety of sources, including:
+The media connector can connect to various sources, including:
 
 | Media source | Example URLs | Notes |
 |--------------| ---------------|-------|
 | Edge attached camera | `file://host/dev/video0`<br/>`file://host/dev/usb0` | No authentication required. The URL refers to the device file. Connects to a node using USB, FireWire, MIPI, or proprietary interface. |
 | IP camera | `rtsp://192.168.178.45:554/stream1` | JPEG over HTTP for snapshots, RTSP/RTCP/RTP/MJPEG-TS for video streams. An IP camera might also expose a standard ONVIF control interface. |
 | Media server | `rtsp://192.168.178.45:554/stream1` | JPEG over HTTP for snapshots, RTSP/RTCP/RTP/MJPEG-TS for video streams. A media server can also serve images and videos using URLs such as `ftp://host/path` or `smb://host/path` |
 | Media file | `http://camera1/snapshot/profile1`<br/>`nfs://server/path/file.extension`<br/>` file://localhost/media/path/file.mkv`  | Any media file with a URL accessible from the cluster. |
-| Media folder | `file://host/path/to/folder/`<br/>`ftp://server/path/to/folder/` | A folder, accessible from the cluster, that contain media files such as snapshots or clips. |
+| Media folder | `file://host/path/to/folder/`<br/>`ftp://server/path/to/folder/` | A folder, accessible from the cluster, that contains media files such as snapshots or clips. |
 
 ## Example uses
 
@@ -34,15 +34,15 @@ Example uses of the media connector include:
 
 - Save video streams to a local file system on your cluster. Use the [What is Azure Container Storage enabled by Azure Arc](/azure/azure-arc/container-storage/overview) to provide a reliable and fault-tolerant solution for uploading the captured video to the cloud for storage or processing.
 
-- Proxy a live video stream from a camera to an endpoint that an operator can access. For security and performance reasons, only the media connector should have direct access to an edge camera. The media connector uses a separate media server component to stream video to an operator's endpoint. This media server can transcode to a variety of protocols such as RTSP, RTCP, SRT, and HLS. You need to deploy your own media server to provide these capabilities.
+- Proxy a live video stream from a camera to an endpoint that an operator can access. For security and performance reasons, only the media connector should have direct access to an edge camera. The media connector uses a separate media server component to stream video to an operator's endpoint. This media server can transcode to various protocols such as RTSP, RTCP, SRT, and HLS. You need to deploy your own media server to provide these capabilities.
 
 ## How does it relate to Azure IoT Operations?
 
 The media connector is part of Azure IoT Operations. The connector deploys to an Arc-enabled Kubernetes cluster on the edge as part of an Azure IoT Operations deployment. The connector interacts with other Azure IoT Operations elements, such as:
 
-- _Asset endpoints_, that are custom resources in your Kubernetes cluster, define connections to assets such as cameras. An asset endpoint configuration includes the URL of the media source, the type of media source, and any credentials needed to access the media source. The media connector uses an asset endpoint to access the media source.
+- _Asset endpoints_ that are custom resources in your Kubernetes cluster define connections to assets such as cameras. An asset endpoint configuration includes the URL of the media source, the type of media source, and any credentials needed to access the media source. The media connector uses an asset endpoint to access the media source.
 
-- _Assets_, in Azure IoT Operations are logical entities that you create to represent a real assets such as cameras. An Azure IoT Operations camera asset can have properties, tags, and video streams.
+- _Assets_, in Azure IoT Operations are logical entities that you create to represent real assets such as cameras. An Azure IoT Operations camera asset can have properties, tags, and video streams.
 
 - The MQTT broker that you can use to publish messages from the connectors to other local or cloud-based components in your solution.
 
diff --git a/articles/iot-operations/discover-manage-assets/overview-onvif-connector.md b/articles/iot-operations/discover-manage-assets/overview-onvif-connector.md
@@ -7,14 +7,19 @@ ms.service: azure-iot-operations
 ms.topic: overview
 ms.date: 11/04/2024
 
-#CustomerIntent: As an industrial edge IT or operations user, I want understand what the connector for ONVIF is so that I can determine whether I can use it in my industrial IoT solution.
+#CustomerIntent: As an industrial edge IT or operations user, I want to understand what the connector for ONVIF is so that I can determine whether I can use it in my industrial IoT solution.
 ---
 
 # What is the Azure IoT Operations connector for ONVIF (preview)?
 
-The connector for ONVIF (preview) for Azure IoT Operations discovers [ONVIF conformant](https://www.onvif.org/profiles-add-ons-specifications/) cameras connected to your Azure IoT Operations instance and registers them in the Azure Device Registry. Once registered, you can manage these cameras by getting and setting properties through the connector. The [media connector](overview-media-connector.md) can access the media sources exposed by these cameras.
+The connector for ONVIF (preview) for Azure IoT Operations discovers [ONVIF conformant](https://www.onvif.org/profiles-add-ons-specifications/) cameras connected to your Azure IoT Operations instance and registers them in the Azure Device Registry. After the camera is registered, examples of management operations include:
 
-Together, the media connector and connector for ONVIF enable you to use Azure IoT Operations to implement use cases such as:
+- Retrieving and updating the configuration of the camera to adjust the output image configuration.
+- Controlling the camera pan, tilt, and zoom (PTZ).
+
+The [media connector](overview-media-connector.md) can access the media sources exposed by these cameras.
+
+Together, the media connector, connector for ONVIF, Azure IoT Operations, and companion services enable you to use Azure IoT Operations to implement use cases such as:
 
 - Wait and dwell time tracking to track the time spent in line by customers.
 - Order accuracy to track that the correct orders are packed by comparing items to POS receipt.
@@ -26,17 +31,17 @@ Together, the media connector and connector for ONVIF enable you to use Azure Io
 The connector for ONVIF enables you to:
 
 - Read camera information and capabilities.
-- Discover the media URIs exposed by a camera.
+- Discover the media URIs exposed by the ONVIF camera.
 - Configure ONVIF devices, for example by updating setting or selecting presets.
-- Respond to events from the cameras, for example when motion is detected.
+- Control the camera hardware by using PTZ commands.
 
 ## How does it relate to Azure IoT Operations?
 
 The connector for ONVIF is part of Azure IoT Operations. The connector deploys to an Arc-enabled Kubernetes cluster on the edge as part of an Azure IoT Operations deployment. The connector interacts with other Azure IoT Operations elements, such as:
 
-- _Asset endpoints_, that are custom resources in your Kubernetes cluster, define connections to assets such as cameras. An asset endpoint configuration includes the URL of the media source, the type of media source, and any credentials needed to access the media source. The media connector uses an asset endpoint to access the media source.
+- _Asset endpoints_ that are custom resources in your Kubernetes cluster, define connections to assets such as cameras. An asset endpoint configuration includes the URL of the media source, the type of media source, and any credentials needed to access the media source. The media connector uses an asset endpoint to access the media source.
 
-- _Assets_, in Azure IoT Operations are logical entities that you create to represent a real assets such as cameras. An Azure IoT Operations ONVIF camera asset identifies the ONVIF network service the camera exposes, such as pan-tilt-zoom (PTZ).
+- _Assets_, in Azure IoT Operations are logical entities that you create to represent real assets such as cameras. An Azure IoT Operations ONVIF camera asset identifies the ONVIF network service the camera exposes, such as PTZ.
 
 - The Azure IoT Operations experience web UI provides a unified experience for you to manage assets such as cameras. You can use the operations experience to configure the assets and asset endpoints that the media connector uses to access media sources.
 
@@ -57,7 +62,7 @@ The connector enables support for the following capabilities:
 
 - Discovery of device information and capabilities.
 - Monitoring events from devices.
-- Discovery of the media URIs exposed by a device. The connector for ONVIF makes these available to the media connector.
+- Discovery of the media URIs exposed by a device. The connector for ONVIF makes these URIs available to the media connector.
 - Imaging control such as filters and receiving  motion and tampering events.
 - Controlling device PTZ.
 
