Skip to content

Commit 7cfdb52

Browse files
authored
Apply suggestions from code review
PR review: Corrected Acrolinx issues
1 parent 560377d commit 7cfdb52

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/iot-operations/discover-manage-assets/concept-assets-asset-endpoints.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ You can create, edit, and delete asset endpoints and assets by using the Azure I
2828

2929
Before you can create an asset, you need to define an asset endpoint profile. An *asset endpoint* is a profile that describes southbound edge connectivity information for one or more assets.
3030

31-
Currently, the only southbound connectors available in Azure IoT Operations are the connector for OPC UA, the media connector (preview), and the connector for ONVIF (preview). Asset endpoints are configurations for a connector that enable it to connect to an assets. For example:
31+
Currently, the only southbound connectors available in Azure IoT Operations are the connector for OPC UA, the media connector (preview), and the connector for ONVIF (preview). Asset endpoints are configurations for a connector that enable it to connect to an asset. For example:
3232

3333
- An asset endpoint for OPC UA stores the information you need to connect to an OPC UA server.
3434
- An asset endpoint for the media connector stores the information you need to connect to a media source.

articles/iot-operations/discover-manage-assets/howto-use-onvif-connector.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ An ONVIF compliant camera connected to your Azure IoT Operations cluster. If you
2727

2828
The connector for ONVIF (preview) uses [asset endpoint and asset](concept-assets-asset-endpoints.md) custom resources to represent the connection and the camera.
2929

30-
For example, use the following Bicep and parameters to to create an asset endpoint that enables discovery of an ONVIF compliant camera at `http://onvif-rtsp-simulator:8000`:
30+
For example, use the following Bicep and parameters to create an asset endpoint that enables discovery of an ONVIF compliant camera at `http://onvif-rtsp-simulator:8000`:
3131

3232
```bicep
3333
metadata description = 'Asset endpoint profile for ONVIF discovery'
@@ -100,7 +100,7 @@ Each **DiscoveredAsset** custom resource represents one of the [ONVIF services](
100100

101101
Each **DiscoveredAssetEndpointProfile** custom resource represents a video stream format that the camera exposes.
102102

103-
Currently, during public preview, you must manually create the **Asset** and **AssetEndpointProfile** custom resources that represent the capabilities of the camera and it's video streams.
103+
Currently, during public preview, you must manually create the **Asset** and **AssetEndpointProfile** custom resources that represent the capabilities of the camera and its video streams.
104104

105105
To create an asset that represents the PTZ capabilities of the camera discovered above, use the following Bicep and parameters:
106106

@@ -156,7 +156,7 @@ The following JSON snippet shows a set of parameter values to use:
156156

157157
These parameters configure:
158158

159-
- 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.
159+
- The name of the asset to create. The `-ptz` suffix is a required convention to indicate that the asset represents the PTZ capabilities of the camera.
160160
- The associated asset endpoint you created previously.
161161

162162
To apply the previous configuration, save the examples above as files, and run the following command:

0 commit comments

Comments
 (0)