Fixing broken links

Author: andrewbrownmsft

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

@@ -54,12 +54,12 @@ The following table lists error codes pertaining to the content service componen
 | Error importing update due to exceeded limit.  |       Cannot import additional update provider.                                     | You've 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've 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've 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.md#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. If you try to use the same compatibility properties with more than one Provider/Name combination, you'll see these errors. To resolve this issue, 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.md#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. If you try to use the same compatibility properties with more than one Provider/Name combination, you'll see these errors. To resolve this issue, 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.md#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. If you try to use the same compatibility properties with more than one Provider/Name combination, you'll see these errors. To resolve this issue, 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 provider with the specified compatibility. | When defining [compatibility properties](import-schema.md#compabilityinfo-object) 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. If you try to use the same compatibility properties with more than one Provider/Name combination, you'll see these errors. To resolve this issue, 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.md#compabilityinfo-object) 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. If you try to use the same compatibility properties with more than one Provider/Name combination, you'll see these errors. To resolve this issue, 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.md#compabilityinfo-object) 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. If you try to use the same compatibility properties with more than one Provider/Name combination, you'll see these errors. To resolve this issue, 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. |
-| "SourceFilePendingMalwareAnalysis"   | A signature was detected in a file being imported that may indicate malware is present.                                             | Content imported into Device Update for IoT Hub is scanned for malware by several different mechanisms. If a signature is identified that is not an exact match for known malware, but has _characteristics_ of malware, the import will fail. Whern this occurs, a unique error message will be returned. The error message contains the description of the suspected 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've removed the malware from any files being imported, you can start the import process again. If you're certain your files are free of malware and continue to see this error, use the [Contact Microsoft Support](troubleshoot-device-update.md#contact) process. |
+| "SourceFilePendingMalwareAnalysis"   | A signature was detected in a file being imported that may indicate malware is present.                                             | Content imported into Device Update for IoT Hub is scanned for malware by several different mechanisms. The import will fail if a scan signature has _characteristics_ of malware, even if there is not an exact match to known malware. When this occurs, a unique error message will be returned. The error message contains the description of the suspected 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've removed the malware from any files being imported, you can start the import process again. If you're certain your files are free of malware and continue to see this error, use the [Contact Microsoft Support](troubleshoot-device-update.md#contact) process. |
 
 **[Next Step: Troubleshoot issues with Device Update](.\troubleshoot-device-update.md)**