This patch fixed 2 spelling errors in the documentation.
Signed-off-by: Chun-Hung Tseng <[email protected]>
---
Documentation/scheduler/sched-nice-design.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/scheduler/sched-nice-design.rst b/Documentation/scheduler/sched-nice-design.rst
index 0571f1b47e64..889bf2b737dc 100644
--- a/Documentation/scheduler/sched-nice-design.rst
+++ b/Documentation/scheduler/sched-nice-design.rst
@@ -60,7 +60,7 @@ within the constraints of HZ and jiffies and their nasty design level
coupling to timeslices and granularity it was not really viable.
The second (less frequent but still periodically occurring) complaint
-about Linux's nice level support was its assymetry around the origo
+about Linux's nice level support was its asymmetry around the origin
(which you can see demonstrated in the picture above), or more
accurately: the fact that nice level behavior depended on the _absolute_
nice level as well, while the nice API itself is fundamentally
--
2.25.1
Chun-Hung Tseng <[email protected]> writes:
> This patch fixed 2 spelling errors in the documentation.
Next time, word this in the imperative form ("Fix two spelling
errors...") and leave out "this patch". Meanwhile...
> Signed-off-by: Chun-Hung Tseng <[email protected]>
> ---
> Documentation/scheduler/sched-nice-design.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/scheduler/sched-nice-design.rst b/Documentation/scheduler/sched-nice-design.rst
> index 0571f1b47e64..889bf2b737dc 100644
> --- a/Documentation/scheduler/sched-nice-design.rst
> +++ b/Documentation/scheduler/sched-nice-design.rst
> @@ -60,7 +60,7 @@ within the constraints of HZ and jiffies and their nasty design level
> coupling to timeslices and granularity it was not really viable.
>
> The second (less frequent but still periodically occurring) complaint
> -about Linux's nice level support was its assymetry around the origo
> +about Linux's nice level support was its asymmetry around the origin
> (which you can see demonstrated in the picture above), or more
Applied, thanks.
jon