Hibernate
/
hibernate-orm
mirror of https://github.com/hibernate/hibernate-orm
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix Documentation typos

This commit is contained in:
Andrea Boriero 2016-02-13 18:45:58 +00:00
parent 85e9f8b206
commit 31cda52178
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/src/main/asciidoc/userguide/chapters/domain/mapping_types.adoc
View File

@ -51,7 +51,7 @@ Value types are further classified into three sub-categories:
Basic types:: in mapping the `Contact` table, all attributes except for name would be basic types. Basic types are discussed in detail in <<chapters/domain/basic_types.adoc#basic,_Basic Types_>>
Embeddable types:: the name attribute is an example of an embeddable type, which is discussed in details in <<chapters/domain/embeddables.adoc#embeddables,_Embeddable Types_>>
Collection types:: although not featured n the aforementioned example, collection types are also a distinct category among value types. Collection types are further discussed in <<chapters/domain/collection.adoc#collections,_Collections_>>
Collection types:: although not featured in the aforementioned example, collection types are also a distinct category among value types. Collection types are further discussed in <<chapters/domain/collection.adoc#collections,_Collections_>>
[[categorization-entity]]
==== Entity types

4
documentation/src/main/asciidoc/userguide/chapters/domain/naming.adoc
View File

@ -30,7 +30,7 @@ in favor of ImplicitNamingStrategy and PhysicalNamingStrategy.
====
At the core, the idea behind each naming strategy is to minimize the amount of
repetitive information a developer must provider for mapping a domain model.
repetitive information a developer must provide for mapping a domain model.
[NOTE]
@ -52,7 +52,7 @@ is important, applications should prefer to not specify a PhysicalNamingStrategy
When an entity does not explicitly name the database table that it maps to, we need
to implicitly determine that table name. Or when a particular attribute does not explicitly name
the database column that it maps to, we need to implicitly determine that column name. There are
examples of the role of the `org.hibernate.boot.model.naming.ImplicitNamingStrategy` contract : to
examples of the role of the `org.hibernate.boot.model.naming.ImplicitNamingStrategy` contract to
determine a logical name when the mapping did not provide an explicit name.
image:images/domain/naming/implicit_naming_strategy_diagram.svg[Implicit Naming Strategy Diagram]