Signed-off-by: Ryan Cheevers <cheeversr0@gmail.com>
---
 Documentation/core-api/housekeeping.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/core-api/housekeeping.rst b/Documentation/core-api/housekeeping.rst
index e5417302774c..92c6e53cea75 100644
--- a/Documentation/core-api/housekeeping.rst
+++ b/Documentation/core-api/housekeeping.rst
@@ -15,7 +15,7 @@ various deferrals etc...
 Sometimes housekeeping is just some unbound work (unbound workqueues,
 unbound timers, ...) that gets easily assigned to non-isolated CPUs.
 But sometimes housekeeping is tied to a specific CPU and requires
-elaborated tricks to be offloaded to non-isolated CPUs (RCU_NOCB, remote
+elaborate tricks to be offloaded to non-isolated CPUs (RCU_NOCB, remote
 scheduler tick, etc...).
 
 Thus, a housekeeping CPU can be considered as the reverse of an isolated
-- 
2.53.0

Ryan Cheevers <cheeversr0@gmail.com> writes:

> Signed-off-by: Ryan Cheevers <cheeversr0@gmail.com>
> ---
>  Documentation/core-api/housekeeping.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/core-api/housekeeping.rst b/Documentation/core-api/housekeeping.rst
> index e5417302774c..92c6e53cea75 100644
> --- a/Documentation/core-api/housekeeping.rst
> +++ b/Documentation/core-api/housekeeping.rst
> @@ -15,7 +15,7 @@ various deferrals etc...
>  Sometimes housekeeping is just some unbound work (unbound workqueues,
>  unbound timers, ...) that gets easily assigned to non-isolated CPUs.
>  But sometimes housekeeping is tied to a specific CPU and requires
> -elaborated tricks to be offloaded to non-isolated CPUs (RCU_NOCB, remote
> +elaborate tricks to be offloaded to non-isolated CPUs (RCU_NOCB, remote
>  scheduler tick, etc...).

Applied, thanks.

jon