Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixed some typos #1001

Open
wants to merge 1 commit into
base: 3.0.x
Choose a base branch
from
Open

fixed some typos #1001

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/src/reference/asciidoc/appendix-reactormigration-examples.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 changes: 3 additions & 3 deletions docs/src/reference/asciidoc/appendix-reactormigration.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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[]
Expand Down
2 changes: 1 addition & 1 deletion docs/src/reference/asciidoc/sm-repository.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion docs/src/reference/asciidoc/whatsnew.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down