1 files changed, 1 insertions, 1 deletions
diff --git a/docs/dev/lsp-extensions.md b/docs/dev/lsp-extensions.md
index d7f287894..b2defa737 100644
--- a/docs/dev/lsp-extensions.md
+++ b/docs/dev/lsp-extensions.md
@@ -238,7 +238,7 @@ As proper cursor positioning is raison-d'etat for `onEnter`, it uses `SnippetTex
 * How to deal with synchronicity of the request?
  One option is to require the client to block until the server returns the response.
  Another option is to do a OT-style merging of edits from client and server.
-  A third option is to do a record-replay: client applies heuristic on enter immediatelly, then applies all user's keypresses.
+  A third option is to do a record-replay: client applies heuristic on enter immediately, then applies all user's keypresses.
  When the server is ready with the response, the client rollbacks all the changes and applies the recorded actions on top of the correct response.
 * How to deal with multiple carets?
 * Should we extend this to arbitrary typed events and not just `onEnter`?

diff --git a/docs/dev/lsp-extensions.md b/docs/dev/lsp-extensions.md index d7f287894..b2defa737 100644 --- a/docs/dev/lsp-extensions.md +++ b/docs/dev/lsp-extensions.md
@@ -238,7 +238,7 @@ As proper cursor positioning is raison-d'etat for `onEnter`, it uses `SnippetTex
238	* How to deal with synchronicity of the request?	238	* How to deal with synchronicity of the request?
239	One option is to require the client to block until the server returns the response.	239	One option is to require the client to block until the server returns the response.
240	Another option is to do a OT-style merging of edits from client and server.	240	Another option is to do a OT-style merging of edits from client and server.
241	A third option is to do a record-replay: client applies heuristic on enter immediatelly, then applies all user's keypresses.	241	A third option is to do a record-replay: client applies heuristic on enter immediately, then applies all user's keypresses.
242	When the server is ready with the response, the client rollbacks all the changes and applies the recorded actions on top of the correct response.	242	When the server is ready with the response, the client rollbacks all the changes and applies the recorded actions on top of the correct response.
243	* How to deal with multiple carets?	243	* How to deal with multiple carets?
244	* Should we extend this to arbitrary typed events and not just `onEnter`?	244	* Should we extend this to arbitrary typed events and not just `onEnter`?