Spring/spring-statemachine
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fixed some typos

Browse Source
This commit is contained in:
Jan Wilhelms
2021-08-24 08:36:29 +02:00
committed by Mahmoud Ben Hassine
parent 7bc67e8e17
commit c41cda42e5
4 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/src/reference/asciidoc/appendix-reactormigration-examples.adoc
View File

@@ -2,4 +2,4 @@
While most of an examples are still same, we've overhauled some of them and
created some new:
* Tunrstile Reactive <<statemachine-examples-turnstilereactive>>
* Turnstile Reactive <<statemachine-examples-turnstilereactive>>

6
docs/src/reference/asciidoc/appendix-reactormigration.adoc
View File

@@ -1,10 +1,10 @@
[appendix]
[[appendix-reactormigrationguide]]
== Reactor Migration Guide
Main task for a work for `3.x` has been to both internally and externally to move and change
Main task for a work for `3.x` has been to both internally and externally move and change
as much as we can from imperative code into a reactive world. This means that some
of a main interfaces has added a new reative methods and most of a internal execution locig
(where applicable) has been moved over to handled by a reactor. Essentially what this means is that thread handling model is considerably different compared to `2.x`. Following chapters
of the main interfaces have added new reative methods and most of a internal execution logic
(where applicable) has been moved over to be handled by a reactor. Essentially what this means is that thread handling model is considerably different compared to `2.x`. Following chapters
go throught all these changes.
include::appendix-reactormigration-communicating.adoc[]

2
docs/src/reference/asciidoc/sm-repository.adoc
View File

@@ -63,7 +63,7 @@ model regarding used table names. Previously, generated table names
always had a prefix of `JPA_REPOSITORY_`, derived from entity class
names. As this caused breaking issues with databases imposing
restrictions on database object lengths, all entity classes have
spesific definitions to force table names. For example,
specific definitions to force table names. For example,
`JPA_REPOSITORY_STATE` is now 'STATE' -- and so on with other
ntity classes.

2
docs/src/reference/asciidoc/whatsnew.adoc
View File

@@ -73,7 +73,7 @@ in a future releases.
[IMPORTANT]
====
Please read an appendix <<appendix-reactormigrationguide>> carefully as it will steer you
through a process of migrating into `3.x` for cases we're not handling internallyl.
through a process of migrating into `3.x` for cases we're not handling internally.
====
At this point most of a documentation has been changed to showcase reactive interfaces