Correct to "following" from "followings" in the sentence "The followings
are the read bandwidths and CPU utilizations depending on different affinity
scope settings on ``kcryptd`` measured over five runs."

Signed-off-by: Attreyee Mukherjee <tintinm2017@gmail.com>
---
 Documentation/core-api/workqueue.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/core-api/workqueue.rst b/Documentation/core-api/workqueue.rst
index 0046af06531a..8c325a640862 100644
--- a/Documentation/core-api/workqueue.rst
+++ b/Documentation/core-api/workqueue.rst
@@ -446,7 +446,7 @@ The command used: ::
 
 There are 24 issuers, each issuing 64 IOs concurrently. ``--verify=sha512``
 makes ``fio`` generate and read back the content each time which makes
-execution locality matter between the issuer and ``kcryptd``. The followings
+execution locality matter between the issuer and ``kcryptd``. The following
 are the read bandwidths and CPU utilizations depending on different affinity
 scope settings on ``kcryptd`` measured over five runs. Bandwidths are in
 MiBps, and CPU util in percents.
-- 
2.34.1

attreyee-muk <tintinm2017@gmail.com> writes:

> Correct to "following" from "followings" in the sentence "The followings
> are the read bandwidths and CPU utilizations depending on different affinity
> scope settings on ``kcryptd`` measured over five runs."
>
> Signed-off-by: Attreyee Mukherjee <tintinm2017@gmail.com>
> ---
>  Documentation/core-api/workqueue.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/core-api/workqueue.rst b/Documentation/core-api/workqueue.rst
> index 0046af06531a..8c325a640862 100644
> --- a/Documentation/core-api/workqueue.rst
> +++ b/Documentation/core-api/workqueue.rst
> @@ -446,7 +446,7 @@ The command used: ::
>  
>  There are 24 issuers, each issuing 64 IOs concurrently. ``--verify=sha512``
>  makes ``fio`` generate and read back the content each time which makes
> -execution locality matter between the issuer and ``kcryptd``. The followings
> +execution locality matter between the issuer and ``kcryptd``. The following
>  are the read bandwidths and CPU utilizations depending on different affinity
>  scope settings on ``kcryptd`` measured over five runs. Bandwidths are in

Applied, thanks.

jon