Update pull-request-policy.md

Commit migrated from https://github.com/dotnet/corefx/commit/1d994feb73fcf57161e5bded92119c0d1b147616

diff --git a/docs/libraries/project-docs/pull-request-policy.md b/docs/libraries/project-docs/pull-request-policy.md
index dd1bc04..a7e87c9 100644 (file)
--- a/docs/libraries/project-docs/pull-request-policy.md
+++ b/docs/libraries/project-docs/pull-request-policy.md
@@ -13,7 +13,7 @@ In case CI indicates test failures which are **highly unlikely** to be caused by
 1. An existing issue in the repository should be searched for. Usually the test method's or the test assembly's name (in case of a crash) are good parameters.
 2. If there's an existing issue, a comment should be placed that includes a) the link to the build, b) the affected configuration (ie `netcoreapp-Windows_NT-Release-x64-Windows.81.Amd64.Open`) and c) the Error message and Stack trace. This is necessary as retention policies are in place that recycle _old_ builds. In case the issue is already closed, it should be reopened and labels should be updated to reflect the current failure state. 
 3. If there's no existing issue, an issue should be created with the same information outlined above.
-4. In a follow-up Pull Request, the failing test(s) should be disabled with the corresponding issue number, e.g. `[ActiveIssue(x)]`, and the tracking issue should be labedeled as `disabled-test`.
+4. In a follow-up Pull Request, the failing test(s) should be disabled with the corresponding issue number, e.g. `[ActiveIssue(x)]`, and the tracking issue should be labeled as `disabled-test`.
 5. A comment should be placed in the original Pull Request that links to the created or updated issues.
 
 There are plenty of possible bugs, e.g. race conditions, where a failure might highlight a real problem and it won't manifest again on a retry. Therefore these steps should be followed for every iteration of the PR build, e.g. before retrying/rebuilding.