Merge pull request #334 from MicrosoftDocs/jken-error-codes-take2

Remaining error codes topics

desktop-src/Debug/system-error-codes--0-499-.md

@@ -9,9 +9,7 @@ ms.date: 07/18/2019
 # System Error Codes (0-499)
 
 > [!NOTE]
-> This information is intended for developers so that the software they write can better deal with errors. If you're experiencing difficulty with an application that you're installing or running, contact customer support for the software that is displaying the error message. To obtain support for a Microsoft product, visit [Microsoft Support](https://support.microsoft.com).
-
-System Error Codes are very broad: each one can occur in one of many hundreds of locations in the system. Consequently, the descriptions of these codes cannot be very specific. Use of these codes requires some amount of investigation and analysis. You need to note both the programmatic and the runtime context in which these errors occur. Because these codes are defined in WinError.h for anyone to use, sometimes the codes are returned by non-system software. And sometimes the code is returned by a function deep in the stack and far removed from your code that is handling the error.
+> This information is intended for developers debugging system errors. For other errors, such as issues with Windows Update, there is a list of resources on the [Error codes](system-error-codes.md) page.
 
 The following list describes [system error codes](system-error-codes.md) (errors 0 to 499). They are returned by the [**GetLastError**](/windows/win32/api/errhandlingapi/nf-errhandlingapi-getlasterror) function when many functions fail. To retrieve the description text for the error in your application, use the [**FormatMessage**](/windows/desktop/api/WinBase/nf-winbase-formatmessage) function with the **FORMAT\_MESSAGE\_FROM\_SYSTEM** flag.
 

desktop-src/Debug/system-error-codes--1000-1299-.md

@@ -9,9 +9,7 @@ ms.date: 07/18/2019
 # System Error Codes (1000-1299)
 
 > [!NOTE]
-> This information is intended for developers so that the software they write can better deal with errors. If you're experiencing difficulty with an application that you're installing or running, contact customer support for the software that is displaying the error message. To obtain support for a Microsoft product, visit [Microsoft Support](https://support.microsoft.com).
-
-System Error Codes are very broad: each one can occur in one of many hundreds of locations in the system. Consequently, the descriptions of these codes cannot be very specific. Use of these codes requires some amount of investigation and analysis. You need to note both the programmatic and the runtime context in which these errors occur. Because these codes are defined in WinError.h for anyone to use, sometimes the codes are returned by non-system software. And sometimes the code is returned by a function deep in the stack and far removed from your code that is handling the error.
+> This information is intended for developers debugging system errors. For other errors, such as issues with Windows Update, there is a list of resources on the [Error codes](system-error-codes.md) page.
 
 The following list describes [system error codes](system-error-codes.md) for errors 1000 to 1299. They are returned by the [**GetLastError**](/windows/win32/api/errhandlingapi/nf-errhandlingapi-getlasterror) function when many functions fail. To retrieve the description text for the error in your application, use the [**FormatMessage**](/windows/desktop/api/WinBase/nf-winbase-formatmessage) function with the **FORMAT\_MESSAGE\_FROM\_SYSTEM** flag.
 

desktop-src/Debug/system-error-codes--1300-1699-.md

@@ -9,9 +9,7 @@ ms.date: 07/18/2019
 # System Error Codes (1300-1699)
 
 > [!NOTE]
-> This information is intended for developers so that the software they write can better deal with errors. If you're experiencing difficulty with an application that you're installing or running, contact customer support for the software that is displaying the error message. To obtain support for a Microsoft product, visit [Microsoft Support](https://support.microsoft.com).
-
-System Error Codes are very broad: each one can occur in one of many hundreds of locations in the system. Consequently, the descriptions of these codes cannot be very specific. Use of these codes requires some amount of investigation and analysis. You need to note both the programmatic and the runtime context in which these errors occur. Because these codes are defined in WinError.h for anyone to use, sometimes the codes are returned by non-system software. And sometimes the code is returned by a function deep in the stack and far removed from your code that is handling the error.
+> This information is intended for developers debugging system errors. For other errors, such as issues with Windows Update, there is a list of resources on the [Error codes](system-error-codes.md) page.
 
 The following list describes [system error codes](system-error-codes.md) for errors 1300 to 1699. They are returned by the [**GetLastError**](/windows/win32/api/errhandlingapi/nf-errhandlingapi-getlasterror) function when many functions fail. To retrieve the description text for the error in your application, use the [**FormatMessage**](/windows/desktop/api/WinBase/nf-winbase-formatmessage) function with the **FORMAT\_MESSAGE\_FROM\_SYSTEM** flag.
 

desktop-src/Debug/system-error-codes--500-999-.md

@@ -9,9 +9,7 @@ ms.date: 07/18/2019
 # System Error Codes (500-999)
 
 > [!NOTE]
-> This information is intended for developers so that the software they write can better deal with errors. If you're experiencing difficulty with an application that you're installing or running, contact customer support for the software that is displaying the error message. To obtain support for a Microsoft product, visit [Microsoft Support](https://support.microsoft.com).
-
-System Error Codes are very broad: each one can occur in one of many hundreds of locations in the system. Consequently, the descriptions of these codes cannot be very specific. Use of these codes requires some amount of investigation and analysis. You need to note both the programmatic and the runtime context in which these errors occur. Because these codes are defined in WinError.h for anyone to use, sometimes the codes are returned by non-system software. And sometimes the code is returned by a function deep in the stack and far removed from your code that is handling the error.
+> This information is intended for developers debugging system errors. For other errors, such as issues with Windows Update, there is a list of resources on the [Error codes](system-error-codes.md) page.
 
 The following list describes [system error codes](system-error-codes.md) (errors 500 to 999). They are returned by the [**GetLastError**](/windows/win32/api/errhandlingapi/nf-errhandlingapi-getlasterror) function when many functions fail. To retrieve the description text for the error in your application, use the [**FormatMessage**](/windows/desktop/api/WinBase/nf-winbase-formatmessage) function with the **FORMAT\_MESSAGE\_FROM\_SYSTEM** flag.