Re: [PATCH] docs: fuse: fix typos in fuse-caches.rst

[Randy Dunlap]

On 11/3/26 1:44 AM, Viacheslav Shevchuk wrote:
> Fix two misspellings of "successfully" and change "then next time"
> to "the next time".
> 
> The misspellings were found with the help of an AI coding assistant
> (Claude Opus 5.5) by grepping Documentation/ for the entries in
> scripts/spelling.txt.
> 
> Signed-off-by: Viacheslav Shevchuk <slavik.a.shevchuk@xxxxxxxxx>

Acked-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
Thanks.

> ---
>  Documentation/filesystems/fuse/fuse-caches.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/filesystems/fuse/fuse-caches.rst b/Documentation/filesystems/fuse/fuse-caches.rst
> index 0778dd3d..d19592c6 100644
> --- a/Documentation/filesystems/fuse/fuse-caches.rst
> +++ b/Documentation/filesystems/fuse/fuse-caches.rst
> @@ -156,11 +156,11 @@ in several occasions:
>  
>  - When a new file system object is created (e.g. ``FUSE_CREATE``,
>    ``FUSE_MKDIR``, etc).
> -- When a lookup is sucessfully performed.
> -- When a dentry is sucessfully revalidated (``->d_revalidate()``).
> +- When a lookup is successfully performed.
> +- When a dentry is successfully revalidated (``->d_revalidate()``).
>  
>  A dentry expiry time can be set to 0, indicating that it is stale. This means
> -that a ``FUSE_LOOKUP`` will be sent to user-space then next time it needs to be
> +that a ``FUSE_LOOKUP`` will be sent to user-space the next time it needs to be
>  looked up. It can be set to 0 in several occasions:
>  
>  - When the user-space FUSE server explicitly requests a dentry to be invalidated

-- 
~Randy