[PATCH] docs: folio_queue: Fix minor typo in folio_queue page

Gopi Krishna Menon posted 1 patch 1 month, 3 weeks ago
Documentation/core-api/folio_queue.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[PATCH] docs: folio_queue: Fix minor typo in folio_queue page
Posted by Gopi Krishna Menon 1 month, 3 weeks ago
Specifically, fix typo 'hese'-> 'these'

Signed-off-by: Gopi Krishna Menon <krishnagopi487@gmail.com>
---
 Documentation/core-api/folio_queue.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/core-api/folio_queue.rst b/Documentation/core-api/folio_queue.rst
index 83cfbc157e49..b7628896d2b6 100644
--- a/Documentation/core-api/folio_queue.rst
+++ b/Documentation/core-api/folio_queue.rst
@@ -44,7 +44,7 @@ Each segment in the list also stores:
  * the size of each folio and
  * three 1-bit marks per folio,
 
-but hese should not be accessed directly as the underlying data structure may
+but these should not be accessed directly as the underlying data structure may
 change, but rather the access functions outlined below should be used.
 
 The facility can be made accessible by::
-- 
2.43.0
Re: [PATCH] docs: folio_queue: Fix minor typo in folio_queue page
Posted by Jonathan Corbet 1 month, 3 weeks ago
Gopi Krishna Menon <krishnagopi487@gmail.com> writes:

> Specifically, fix typo 'hese'-> 'these'
>
> Signed-off-by: Gopi Krishna Menon <krishnagopi487@gmail.com>
> ---
>  Documentation/core-api/folio_queue.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/core-api/folio_queue.rst b/Documentation/core-api/folio_queue.rst
> index 83cfbc157e49..b7628896d2b6 100644
> --- a/Documentation/core-api/folio_queue.rst
> +++ b/Documentation/core-api/folio_queue.rst
> @@ -44,7 +44,7 @@ Each segment in the list also stores:
>   * the size of each folio and
>   * three 1-bit marks per folio,
>  
> -but hese should not be accessed directly as the underlying data structure may
> +but these should not be accessed directly as the underlying data structure may
>  change, but rather the access functions outlined below should be used.

Applied, thanks.

jon