Skip to content

Fix typos #48

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

Merged
merged 1 commit into from
Jan 1, 2020
Merged

Fix typos #48

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 README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -257,7 +257,7 @@ This change might be calculated by dirty checking or we might just override enti
Third option is _Let's make implicit explicit_ and actually call this state change A->B an **event**.
After all, event-driven architecture is all about promoting state changes as domain events.

Thanks to this our domain model may become immutable and just return events as results of invocking a command like so:
Thanks to this our domain model may become immutable and just return events as results of invoking a command like so:

```java
public BookPlacedOnHold placeOnHold(AvailableBook book) {
Expand Down
4 changes: 2 additions & 2 deletions docs/design-level.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ in **book hold failed** event, as it is depicted below:

![Holding example 2](images/dl/holding/example-2.png)

Taking a look at the domain description again, we find out that each patron can have no more than 1 **overdue checkouts**.
Taking a look at the domain description again, we find out that each patron can have no more than 2 **overdue checkouts**.
In such situation, every attempt to **place a book on hold** should fail:

![Holding example 3](images/dl/holding/example-3.png)
Expand Down Expand Up @@ -53,7 +53,7 @@ And here is the last example, partially covered before:

![Holding example 6](images/dl/holding/example-6.png)

### Regular patron
### Researcher patron

In the previous part of this paragraph we focused on a *regular patron* only. Let's have a look at *researcher patron* now.
The domain description clearly states that **any** patron with more than 2 **overdue checkouts** will get a rejection
Expand Down