Documentation: ACPI: fix spelling mistakes

Signed-off-by: Flavio Suligoi <f.suligoi@asem.it>
---
 Documentation/firmware-guide/acpi/acpi-lid.rst       | 8 ++++----
 Documentation/firmware-guide/acpi/method-tracing.rst | 2 +-
 2 files changed, 5 insertions(+), 5 deletions(-)

On Tue, Nov 10, 2020 at 2:03 PM Flavio Suligoi <f.suligoi@asem.it> wrote:
>

> Signed-off-by: Flavio Suligoi <f.suligoi@asem.it>

> ---

>  Documentation/firmware-guide/acpi/acpi-lid.rst       | 8 ++++----

>  Documentation/firmware-guide/acpi/method-tracing.rst | 2 +-

>  2 files changed, 5 insertions(+), 5 deletions(-)

>

> diff --git a/Documentation/firmware-guide/acpi/acpi-lid.rst b/Documentation/firmware-guide/acpi/acpi-lid.rst

> index 874ce0ed340d..71b9af13a048 100644

> --- a/Documentation/firmware-guide/acpi/acpi-lid.rst

> +++ b/Documentation/firmware-guide/acpi/acpi-lid.rst

> @@ -19,9 +19,9 @@ report the "current" state of the lid as either "opened" or "closed".

>

>  For most platforms, both the _LID method and the lid notifications are

>  reliable. However, there are exceptions. In order to work with these

> -exceptional buggy platforms, special restrictions and expections should be

> +exceptional buggy platforms, special restrictions and exceptions should be

>  taken into account. This document describes the restrictions and the

> -expections of the Linux ACPI lid device driver.

> +exceptions of the Linux ACPI lid device driver.

>

>

>  Restrictions of the returning value of the _LID control method

> @@ -46,7 +46,7 @@ state is changed to "closed". The "closed" notification is normally used to

>  trigger some system power saving operations on Windows. Since it is fully

>  tested, it is reliable from all AML tables.

>

> -Expections for the userspace users of the ACPI lid device driver

> +Exceptions for the userspace users of the ACPI lid device driver

>  ================================================================

>

>  The ACPI button driver exports the lid state to the userspace via the

> @@ -100,7 +100,7 @@ use the following kernel parameter:

>  C. button.lid_init_state=ignore:

>     When this option is specified, the ACPI button driver never reports the

>     initial lid state and there is a compensation mechanism implemented to

> -   ensure that the reliable "closed" notifications can always be delievered

> +   ensure that the reliable "closed" notifications can always be delivered

>     to the userspace by always pairing "closed" input events with complement

>     "opened" input events. But there is still no guarantee that the "opened"

>     notifications can be delivered to the userspace when the lid is actually

> diff --git a/Documentation/firmware-guide/acpi/method-tracing.rst b/Documentation/firmware-guide/acpi/method-tracing.rst

> index 0aa7e2c5d32a..6ab6c0964042 100644

> --- a/Documentation/firmware-guide/acpi/method-tracing.rst

> +++ b/Documentation/firmware-guide/acpi/method-tracing.rst

> @@ -98,7 +98,7 @@ subject to change::

>     [    0.188903]   exdebug-0398 ex_trace_point        : Method End [0xf58394d8:\_SB.PCI0.LPCB.ECOK] execution.

>

>  Developers can utilize these special log entries to track the AML

> -interpretion, thus can aid issue debugging and performance tuning. Note

> +interpretation, thus can aid issue debugging and performance tuning. Note

>  that, as the "AML tracer" logs are implemented via ACPI_DEBUG_PRINT()

>  macro, CONFIG_ACPI_DEBUG is also required to be enabled for enabling

>  "AML tracer" logs.

> --


Applied as 5.10-rc material, thanks!