From 0a61b4a076733cdb838a3d3184910915b6c44dac Mon Sep 17 00:00:00 2001 From: Kim Shrier Date: Mon, 2 Sep 2024 22:51:03 -0600 Subject: [PATCH] docs: fix minor typos in the memory management section (#22151) --- doc/docs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/docs.md b/doc/docs.md index 17ecedbc16..adca0264c1 100644 --- a/doc/docs.md +++ b/doc/docs.md @@ -4851,7 +4851,7 @@ Just as the compiler frees C data types with C's `free()`, it will statically in Autofree can be enabled with an `-autofree` flag. For developers willing to have more low level control, autofree can be disabled with -`-manualfree`, or by adding a `[manualfree]` on each function that wants manage its +`-manualfree`, or by adding a `[manualfree]` on each function that wants to manage its memory manually. (See [attributes](#attributes)). > [!NOTE] @@ -4963,7 +4963,7 @@ Here `a` is stored on the stack since its address never leaves the function `f() However a reference to `b` is part of `e` which is returned. Also a reference to `c` is returned. For this reason `b` and `c` will be heap allocated. -Things become less obvious when a reference to an object is passed as function argument: +Things become less obvious when a reference to an object is passed as a function argument: ```v struct MyStruct {