diff --git a/08_EML_ABAP_for_RAP.md b/08_EML_ABAP_for_RAP.md
index c20339b..61b93af 100644
--- a/08_EML_ABAP_for_RAP.md
+++ b/08_EML_ABAP_for_RAP.md
@@ -546,7 +546,7 @@ in [late
numbering](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenrap_late_numbering_glosry.htm "Glossary Entry")
scenarios. The draft indicator
[`%is_draft`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapderived_types_is_draft.htm)
-is only available in the context of
+is only reelvant in the context of
[draft](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenbdl_with_draft.htm).
Find more details on the available components in section [Components of
@@ -584,7 +584,7 @@ Bullet points on selected `%` components:
draft scenario. In doing so, you can avoid lots of adaptations
in your code by manually adding the indicator.
- [`%control`](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abapderived_types_control.htm)
- - Component group that, for example, contains the names of all key
+ - Component group that, in certain contexts and for example (it depends on the context what it contains), contains the names of all key
and data fields of a RAP BO instance which indicate flags.
- Used to get information on which fields are provided or set a
flag for which fields are requested by RAP BO providers or RAP
diff --git a/13_Program_Flow_Logic.md b/13_Program_Flow_Logic.md
index 735eb95..6deeb2d 100644
--- a/13_Program_Flow_Logic.md
+++ b/13_Program_Flow_Logic.md
@@ -571,7 +571,7 @@ Regarding the exiting of procedures, note the hint mentioned above. The use of `
- As mentioned, there are predefined exception classes like `CX_SY_ZERODIVIDE` for divisions by zero. However, you can create your own exception classes so that you can react on issues that are specific to your ABAP program. The exception class must, as stated above, be derived from one of the three abstract classes:
- `CX_STATIC_CHECK`: For forcing users to handle exceptions.
Generally speaking, exceptions that can occur in procedures should be handled locally there in the implementation or be declared explicitly in the [procedure interface](https://help.sap.com/doc/abapdocu_latest_index_htm/latest/en-US/index.htm?file=abenparameter_interface_glosry.htm) so that a caller knows which error situations can be expected. Exception classes of type `CX_STATIC_CHECK` enforce this. A check is carried out statically at compile time. Users of a procedure are then forced to either handle the exception locally in a `TRY` control structure or the users declare the exception themselves in their procedure interface to propagate the exception to their users. If this is not the case, a warning is produced.
- - As an example, a method signature might look as follows. The addition `RAISING` in method signatures are used to declare one or more class-based exceptions that can be propagated from the method to the caller.
+ - As an example, a method signature might look as follows. The addition `RAISING` in method signatures is used to declare one or more class-based exceptions that can be propagated from the method to the caller.
- When users of this method implement the method, they are made aware of the fact that an error situation can occur and a particular exception can be raised. The assumption is that `CX_SOME_ERROR` is derived from `CX_STATIC_CHECK`. Users of the method should then prepare the code accordingly.
```abap
"Method definition using the RAISING parameter
diff --git a/14_ABAP_Unit_Tests.md b/14_ABAP_Unit_Tests.md
index 18052bc..7b623ea 100644
--- a/14_ABAP_Unit_Tests.md
+++ b/14_ABAP_Unit_Tests.md
@@ -11,7 +11,7 @@
- [Handling Dependencies](#handling-dependencies)
- [Test Seams](#test-seams)
- [Running and Evaluating ABAP Unit Tests](#running-and-evaluating-abap-unit-tests)
- - [More information](#more-information)
+ - [More Information](#more-information)
- [Executable Example](#executable-example)
@@ -19,7 +19,7 @@ This cheat sheet contains basic information about [unit testing](https://help.sa
> **💡 Note**
> - This cheat sheet focuses on testing methods.
-> - See the [More Information](#-more-information) section for links to more in-depth information.
+> - See the [More Information](#more-information) section for links to more in-depth information.
> - The executable examples are **not** suitable role models for ABAP unit tests. They are intended to give you a rough idea. You should always work out your own solution for each individual case.
## Unit Tests in ABAP
@@ -577,7 +577,7 @@ For more information about evaluating ABAP unit test results, see [here](https:/
(back to top)
-## More information
+## More Information
- [ABAP Unit in the ABAP Keyword Documentation](https://help.sap.com/doc/abapdocu_cp_index_htm/CLOUD/en-US/index.htm?file=abenabap_unit.htm)
- [openSAP course: Writing Testable Code for ABAP](https://open.sap.com/courses/wtc1.OpenSAP+WTC1_W1U5+Writing+Testable+Code+for+ABAPComent)
diff --git a/README.md b/README.md
index 2e4fced..a4c992b 100644
--- a/README.md
+++ b/README.md
@@ -174,7 +174,7 @@ Use the standalone version of the abapGit report to import the demo examples of
> **💡 Note**
>- Check the notes on the context and the ABAP syntax used that are included as comments in the class.
->- Due to the amount of output in the console, the examples include numbers (e.g. 1) ..., 2) ..., 3) ...) that represent the header of eaxh example code section. Also, in most cases, the variable name is displayed in the console. Therefore, to find the relevant output in the console more easily and quickly, simply search the console for the number (e.g. search for `3)` for the particular output) or variable name (`CTRL+F` in the console), or use breakpoints in the code to check variables in the debugger.
+>- Due to the amount of output in the console, the examples include numbers (e.g. 1) ..., 2) ..., 3) ...) that represent the header of each example code section. Also, in most cases, the variable name is displayed in the console. Therefore, to find the relevant output in the console more easily and quickly, simply search the console for the number (e.g. search for `3)` for the particular output) or variable name (`CTRL+F` in the console), or use breakpoints in the code to check variables in the debugger.
>- You may want to clear the console by right-clicking in the console and choosing `Clear` before running another demo class to avoid confusing the output of multiple classes.