From 4c45844aba2fa50395575e1b7755c1ee32065fb9 Mon Sep 17 00:00:00 2001 From: Martin von Zweigbergk Date: Sun, 9 Jan 2022 22:02:44 -0800 Subject: [PATCH] docs: fix a typo in concurrency doc --- docs/technical/concurrency.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/technical/concurrency.md b/docs/technical/concurrency.md index 161c4c71d..b765baabd 100644 --- a/docs/technical/concurrency.md +++ b/docs/technical/concurrency.md @@ -29,7 +29,7 @@ early: every command that may modify the repo takes a lock at the very beginning. However, that means that operations that wouldn't actually conflict would still have to wait for each other. The user experience can be improved by using finer-grained locks and/or taking the locks later. The drawback of that is -complexity. For example, ou need to verify that any assumptions you made before +complexity. For example, you need to verify that any assumptions you made before locking are still valid. To avoid depending on lock files, Jujutsu takes a different approach by