Skip to content

Commit 0930fb3

Browse files
Cliff Evansgavinking
authored andcommitted
Documentation: Small fixes for typo and grammar
1 parent ac4441a commit 0930fb3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

documentation/src/main/asciidoc/introduction/Entities.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -906,7 +906,7 @@ In fact, Oracle doesn't have `DATE` or `TIME` types--every date or time must be
906906
| `OffsetDateTime`, `ZonedDateTime` | `TIMESTAMP WITH TIME ZONE` | `TIMESTAMP` 🙄 | `DATETIMEOFFSET` | `TIMESTAMP WITH TIME ZONE`
907907
|====
908908

909-
On the other hand, there are no perfectly natural mappings for `Instant` and `Duration` on must databases.
909+
On the other hand, there are no perfectly natural mappings for `Instant` and `Duration` on most databases.
910910
By default:
911911

912912
- `Duration` is mapped to a column of type `NUMERIC(21)` holding the length of the duration in nanoseconds, and
@@ -1095,7 +1095,7 @@ We'll explain the effect of these members as we consider the various types of as
10951095

10961096
It's not a requirement to represent _every_ foreign key relationship as an association at the Java level.
10971097
It's perfectly acceptable to replace a `@ManyToOne` mapping with a basic-typed attribute holding an identifier, if it's inconvenient to think of this relationship as an association at the Java level.
1098-
That said, it's possible to take this idea way to far.
1098+
That said, it's possible to take this idea way too far.
10991099

11001100

11011101
.💀 Aggregates 💀

0 commit comments

Comments
 (0)