wingo pushed a commit to branch wip-whippet
in repository guile.
commit cc6b1c1fb590454f271550fb1ddb92cf0de6cb20
Author: Andy Wingo <wi...@igalia.com>
AuthorDate: Sat Jul 27 22:28:55 2024 +0200
typos
---
doc/collector-pcc.md | 6 +++---
doc/collectors.md | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/collector-pcc.md b/doc/collector-pcc.md
index a55b0fa4f..61af6c4a5 100644
--- a/doc/collector-pcc.md
+++ b/doc/collector-pcc.md
@@ -6,9 +6,9 @@ and multiple tracing threads.
Like `semi`, `pcc` traces by evacuation: it moves all live objects on
every collection. (Exception: objects larger than 8192 bytes are
-placed into a partitioned space traces by marking in place instead of
-copying.) Evacuation requires precise roots, so if your embedder does
-not support precise roots, `pcc` is not for you.
+placed into a partitioned space which traces by marking in place instead
+of copying.) Evacuation requires precise roots, so if your embedder
+does not support precise roots, `pcc` is not for you.
Again like `semi`, `pcc` generally requires a heap size at least twice
as large as the maximum live heap size, and performs best with ample
diff --git a/doc/collectors.md b/doc/collectors.md
index 77e4206ec..81af46e59 100644
--- a/doc/collectors.md
+++ b/doc/collectors.md
@@ -24,7 +24,7 @@ mutator/embedder bugs. Then if memory is tight, switch to
`parallel-whippet`, possibly `parallel-generational-whippet`.
If you are writing a new project, you have a choice as to whether to pay
-the development cost of precise roots or not. If choose to not have
+the development cost of precise roots or not. If you choose to not have
precise roots, then go for `stack-conservative-parallel-whippet`
directly.
