From 9b455d371b268e9b826e83ff6e7dac1914d55f94 Mon Sep 17 00:00:00 2001 From: Mark Lodato Date: Tue, 25 Jan 2022 10:47:22 -0500 Subject: [PATCH] Fix micro typo in async/unsafe function docs **This Commit** Changes "callers responsibility" to "caller's responsibility". **Why?** Just saw it while reading and figured it was a typo. --- src/items/functions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/items/functions.md b/src/items/functions.md index 537effb03..a2995bcea 100644 --- a/src/items/functions.md +++ b/src/items/functions.md @@ -317,7 +317,7 @@ other unsafe function, these conditions may extend beyond the initial call itself -- in the snippet above, for example, the `unsafe_example` function took a pointer `x` as argument, and then (when awaited) dereferenced that pointer. This implies that `x` would have to be -valid until the future is finished executing, and it is the callers +valid until the future is finished executing, and it is the caller's responsibility to ensure that. ## Attributes on functions