From 73c8b5431cce7eadba44cd0f0e30e1192464dd1b Mon Sep 17 00:00:00 2001 From: JounQin Date: Thu, 1 Feb 2018 20:22:05 +0800 Subject: [PATCH] Typo fix: synchornous -> synchronous (#7177) --- docs/concepts/api-extension/custom-resources.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/api-extension/custom-resources.md b/docs/concepts/api-extension/custom-resources.md index a7a0ccbbef..2d83b396b9 100644 --- a/docs/concepts/api-extension/custom-resources.md +++ b/docs/concepts/api-extension/custom-resources.md @@ -57,7 +57,7 @@ In a Declarative API, typically: Imperative APIs are not declarative. Signs that your API might not be declarative include: - - The client says "do this", and then gets a synchornous response back when it is done. + - The client says "do this", and then gets a synchronous response back when it is done. - The client says "do this", and then gets an operation ID back, and has to check a separate Operation objects to determine completion of the request. - You talk about Remote Procedure Calls (RPCs). - Directly storing large amounts of data (e.g. > a few kB per object, or >1000s of objects).