From 10e76a2d612221ecb161e406a397e1fc698d5fdf Mon Sep 17 00:00:00 2001 From: Janne Valkealahti Date: Sun, 11 Oct 2020 14:27:03 +0100 Subject: [PATCH] Fix typos in docs - Fixes #875 - Fixes #877 --- docs/src/reference/asciidoc/sm-config.adoc | 2 +- docs/src/reference/asciidoc/sm-context.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/reference/asciidoc/sm-config.adoc b/docs/src/reference/asciidoc/sm-config.adoc index db9fef80..62a96b53 100644 --- a/docs/src/reference/asciidoc/sm-config.adoc +++ b/docs/src/reference/asciidoc/sm-config.adoc @@ -445,7 +445,7 @@ You can also have multiple transitions originate from a join state. It this case, we advise you to use guards and define your guards such that only one guard evaluates to `TRUE` at any given time. Otherwise, transition behavior is not predictable. This is shown in the following example, where the guard -checks whwther the extended state has variables: +checks whether the extended state has variables: ==== [source,java,indent=0] diff --git a/docs/src/reference/asciidoc/sm-context.adoc b/docs/src/reference/asciidoc/sm-context.adoc index 18babcbf..894cf88f 100644 --- a/docs/src/reference/asciidoc/sm-context.adoc +++ b/docs/src/reference/asciidoc/sm-context.adoc @@ -114,7 +114,7 @@ include::samples/DocsConfigurationSampleTests4.java[tags=snippetB] ==== You can access the rest of the `StateContext` content. -Tke number and order of the parameters does not matter. +The number and order of the parameters does not matter. The following example shows how to access the various parts of the `StateContext` content: ====