Modifying compat and limit errors

Author: andrewbrownmsft

articles/iot-hub-device-update/device-update-error-codes.md

@@ -51,13 +51,12 @@ The following table lists error codes pertaining to the content service componen
 | "CannotDownload"              | Cannot download import manifest.                                           | Check to make sure the URL for the import manifest file is still valid. |
 | "CannotParse"                 | Cannot parse import manifest.                                              | Check your import manifest for accuracy against the schema defined in the [import update](./create-update.md) documentation. |
 | "UnsupportedVersion"          | Import manifest schema version is not supported.                           | Make sure your import manifest is using the latest schema defined in the [import update](./create-update.md) documentation. |
-| "UpdateLimitExceeded"         | Error importing update due to exceeded limit.                              | You have reached a [limit](device-update-limits.md) on the number of different Providers, Names or Versions allowed in your instance of Device Update for IoT Hub. Delete some updates from your instance and try again. |
-| "UpdateProvider"              | Cannot import a new update provider.                                       | You have reached a [limit](device-update-limits.md) on the number of different __Providers__ allowed in your instance of Device Update for IoT Hub. Delete some updates from your instance and try again. |
-| "UpdateName"                  | Cannot import a new update name for the specified provider.                | You have reached a [limit](device-update-limits.md) on the number of different __Names__ allowed under one Provider in your instance of Device Update for IoT Hub. Delete some updates from your instance and try again. |
-| "UpdateVersion"               | Cannot import a new update version for the specified provider and name.    | You have reached a [limit](device-update-limits.md) on the number of different __Versions__ allowed under one Provider and Name in your instance of Device Update for IoT Hub. Delete some updates with that Name from your instance and try again. |
-| "UpdateProviderCompatibility" | Cannot import additional update provider with the specified compatibility. | When defining device manufacturer and device model compatibility properties in an import manifest, keep in mind that Device Update for IoT Hub supports a single Provider and Name combination for a given manufacturer/model. This means if you try to use the same manufacturer/model compatibility properties with more than one Provider/Name combination, you will see these errors. To resolve this, make sure that all updates for a given device (as defined by manufacturer/model) use the same Provider and Name. While not required, you may want to consider making the Provider the same as the manufacturer and the Name the same as the model, just for simplicity. |
-| "UpdateNameCompatibility"     | Cannot import additional update name with the specified compatibility.     | When defining device manufacturer and device model compatibility properties in an import manifest, keep in mind that Device Update for IoT Hub supports a single Provider and Name combination for a given manufacturer/model. This means if you try to use the same manufacturer/model compatibility properties with more than one Provider/Name combination, you will see these errors. To resolve this, make sure that all updates for a given device (as defined by manufacturer/model) use the same Provider and Name. While not required, you may want to consider making the Provider the same as the manufacturer and the Name the same as the model, just for simplicity. |
-| "UpdateVersionCompatibility"  | Cannot import additional update version with the specified compatibility.  | When defining device manufacturer and device model compatibility properties in an import manifest, keep in mind that Device Update for IoT Hub supports a single Provider and Name combination for a given manufacturer/model. This means if you try to use the same manufacturer/model compatibility properties with more than one Provider/Name combination, you will see these errors. To resolve this, make sure that all updates for a given device (as defined by manufacturer/model) use the same Provider and Name. While not required, you may want to consider making the Provider the same as the manufacturer and the Name the same as the model, just for simplicity. |
+| Error importing update due to exceeded limit.  |       Cannot import additional update provider.                                     | You have reached a [limit](device-update-limits.md) on the number of different __Providers__ allowed in your instance of Device Update for IoT Hub. Delete some updates from your instance and try again. |
+| Error importing update due to exceeded limit.                  | Cannot import additional update name for the specified provider.                | You have reached a [limit](device-update-limits.md) on the number of different __Names__ allowed under one Provider in your instance of Device Update for IoT Hub. Delete some updates from your instance and try again. |
+| Error importing update due to exceeded limit.               | Cannot import additional update version for the specified provider and name.    | You have reached a [limit](device-update-limits.md) on the number of different __Versions__ allowed under one Provider and Name in your instance of Device Update for IoT Hub. Delete some updates with that Name from your instance and try again. |
+| Error importing update due to exceeded limit. | Cannot import additional update provider with the specified compatibility. | When defining [compatibility properties](import-schema#compabilityinfo-object.md) in an import manifest, keep in mind that Device Update for IoT Hub supports a single Provider and Name combination for a given set of compatibility properties. This means if you try to use the same compatibility properties with more than one Provider/Name combination, you will see these errors. To resolve this, make sure that all updates for a given device (as defined by compatibility properties) use the same Provider and Name. |
+| Error importing update due to exceeded limit.     | Cannot import additional update name with the specified compatibility.     | When defining device [compatibility properties](import-schema#compabilityinfo-object.md) in an import manifest, keep in mind that Device Update for IoT Hub supports a single Provider and Name combination for a given set of compatibility properties. This means if you try to use the same compatibility properties with more than one Provider/Name combination, you will see these errors. To resolve this, make sure that all updates for a given device (as defined by compatibility properties) use the same Provider and Name. |
+| Error importing update due to exceeded limit.  | Cannot import additional update version with the specified compatibility.  | When defining device [compatibility properties](import-schema#compabilityinfo-object.md) in an import manifest, keep in mind that Device Update for IoT Hub supports a single Provider and Name combination for a given set of compatibility properties. This means if you try to use the same compatibility properties with more than one Provider/Name combination, you will see these errors. To resolve this, make sure that all updates for a given device (as defined by compatibility properties) use the same Provider and Name. |
 | "CannotProcessUpdateFile"     | Error processing source file.                                              |                                    |
 | "ContentFileCannotDownload"   | Cannot download source file.                                               | Check to make sure the URL for the update file(s) is still valid. |
 | "SourceFileMalwareDetected"   | A known malware signature was detected in a file being imported.                                             | Content imported into Device Update for IoT Hub is scanned for malware by several different mechanisms. If a known malware signature is identified, the import will fail and a unique error message will be returned. The error message contains the description of the malware signature, and a file hash for each file where the signature was detected. You can use the file hash to find the exact file being flagged, and use the description of the malware signature to check that file for malware. <br><br>Once you have removed the malware from any files being imported, you can start the import process again. |