From 01778992aadc5624c5eb8a5ab6ecdf909fcb0dd7 Mon Sep 17 00:00:00 2001
From: Stewart-YU <30410021+stewart-yu@users.noreply.github.com>
Date: Tue, 8 Aug 2017 21:06:25 +0800
Subject: [PATCH] Update review-issues.md

spelling mistake
---
 docs/home/contribute/review-issues.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/home/contribute/review-issues.md b/docs/home/contribute/review-issues.md
index d6cc0bdb01..815edff9c9 100644
--- a/docs/home/contribute/review-issues.md
+++ b/docs/home/contribute/review-issues.md
@@ -55,7 +55,7 @@ The following labels and definitions should be used to prioritize issues. If you
 ## Handling special issue types
 
 ### Duplicate issues
-If a single problem has one or more issues open for it, the problem should be consolodated into a single issue. You should decide which issue to keep open (or open a new issue), port over all relevant information, link related issues, and close all the other issues that describe the same problem. Only having a single issue to work on will help reduce confusion and avoid duplicating work on the same problem.
+If a single problem has one or more issues open for it, the problem should be consolidated into a single issue. You should decide which issue to keep open (or open a new issue), port over all relevant information, link related issues, and close all the other issues that describe the same problem. Only having a single issue to work on will help reduce confusion and avoid duplicating work on the same problem.
 
 ### Dead link issues
 Depending on where the dead link is reported, different actions are required to resolve the issue. Dead links in the API and Kubectl docs are automation issues and should be assigned a P1 until the problem can be fully understood. All other dead links are issues that need to be manually fixed and can be assigned a P3.