Refine asset endpoint

Author: dominicbetts

articles/iot-operations/develop-edge-apps/overview-iot-operations-sdks.md

@@ -78,7 +78,7 @@ The SDKs supports the following application types:
 | Application type | Description |
 |-|-|
 | [Edge application](https://github.com/Azure/iot-operations-sdks/blob/main/doc/edge_application/README.md) | A generic edge application that needs to interface with various Azure IoT Operations services such as the MQTT broker and state store. The SDKs provides convenient clients to simplify the development experience. </br></br>*An Edge Application is a customer managed artifact, including deployment to the cluster and monitoring execution.* |
-| [Akri connector](https://github.com/Azure/iot-operations-sdks/blob/main/doc/akri_connector/README.md)</br>*(in development)*| A specialized edge application deployed by the Akri Operator and designed to interface with on-premises asset endpoints. The Akri connector is responsible for discovering assets available via the endpoint, and relaying information to and from those assets. </br></br>*The Akri connector's deployment is managed automatically by the Akri Operator.* |
+| [Akri connector](https://github.com/Azure/iot-operations-sdks/blob/main/doc/akri_connector/README.md)</br>*(in development)*| A specialized edge application deployed by the Akri Operator and designed to interface with on-premises devices. The Akri connector is responsible for discovering assets available via the endpoint, and relaying information to and from those assets. </br></br>*The Akri connector's deployment is managed automatically by the Akri Operator.* |
 
 > [!NOTE]
 > The Akri connector is part of the Akri services (preview), which is under active development and will be available soon.

articles/iot-operations/discover-manage-assets/overview-manage-assets.md

@@ -72,18 +72,8 @@ An operator configures and manages devices and namespace assets in the operation
 
 To learn more, see [Define assets and devices](concept-assets-devices.md).
 
-Previous versions of Azure IoT Operations used the term *asset endpoint* to refer to the configuration resource that encapsulated the connection information required to connect to a physical device or asset and the term *asset* to refer to the configuration resource that encapsulated information about the data that a physical asset or device exchanges with IoT Operations. Devices offer greater flexibility and more capabilities than asset endpoints, such the ability to define multiple endpoints within a single device. The current version of Azure IoT Operations supports the use of both devices and asset endpoints, but the recommended approach is to use devices.
-
-Assets associated with a device are known as *namespace assets*, assets that are associated with an asset endpoint are simply known as *assets*. The following table shows the differences between devices and asset endpoints:
-
-| Azure IoT Operations version | Devices supported | Asset endpoints supported |
-|-----------------------------|-------------------|--------------------------|
-| v1.1.x and before           | No                | Yes                      |
-| v1.2.x and later            | Yes (recommended) | Yes                      |
-
-To view the asset endpoint documentation, see [Asset management overview](https://go.microsoft.com/fwlink/?linkid=2328508&clcid=0x409) on the previous versions site.
-
-In the current version of Azure IoT Operations, you can continue to manage asset endpoints and assets in the operations experience web UI and by using the Azure CLI.
+> [!TIP]
+> Devices replace the asset endpoints from previous versions of Azure IoT Operations. To view the asset endpoint documentation, see [Asset management overview](https://go.microsoft.com/fwlink/?linkid=2328508&clcid=0x409) on the previous versions site.
 
 ## Understand services for managing devices and namespace assets
 

articles/iot-operations/troubleshoot/troubleshoot.md

@@ -151,7 +151,7 @@ This error occurs when Azure IoT Operations tries to synchronize a secret from A
 
 An OPC UA server connection fails with a `BadSecurityModeRejected` error if the connector tries to connect to a server that only exposes endpoints with no security. There are two options to resolve this issue:
 
-- Overrule the restriction by explicitly setting the following values in the additional configuration for the asset endpoint profile:
+- Overrule the restriction by explicitly setting the following values in the additional configuration for the device:
 
     | Property | Value |
     |----------|-------|
@@ -162,9 +162,9 @@ An OPC UA server connection fails with a `BadSecurityModeRejected` error if the
 
 ## Troubleshoot OPC PLC simulator
 
-### The OPC PLC simulator doesn't send data to the MQTT broker after you create an asset endpoint for it
+### The OPC PLC simulator doesn't send data to the MQTT broker after you create a device for it
 
-To work around this issue, run the following command to set `autoAcceptUntrustedServerCertificates=true` for the asset endpoint:
+To work around this issue, run the following command to set `autoAcceptUntrustedServerCertificates=true` for the device endpoint:
 
 ```bash
 ENDPOINT_NAME=<name-of-you-endpoint-here>
@@ -177,7 +177,7 @@ kubectl patch AssetEndpointProfile $ENDPOINT_NAME \
 > [!CAUTION]
 > Don't use this configuration in production or preproduction environments. Exposing your cluster to the internet without proper authentication might lead to unauthorized access and even DDOS attacks.
 
-You can patch all your asset endpoints with the following command:
+You can patch all your devices with the following command:
 
 ```bash
 ENDPOINTS=$(kubectl get AssetEndpointProfile -n azure-iot-operations --no-headers -o custom-columns=":metadata.name")