HHH-14927 fix other obvious defects in user guide

documentation/src/main/asciidoc/userguide/Bibliography.adoc

@@ -2,5 +2,5 @@
 
 [bibliography]
 - [[[PoEAA]]] Martin Fowler. https://www.martinfowler.com/books/eaa.html[Patterns of Enterprise Application Architecture].
-  Addison-Wesley Publishing Company. 2003.
-- [[[JPwH]]] Christian Bauer & Gavin King. https://www.manning.com/books/java-persistence-with-hibernate-second-edition[Java Persistence with Hibernate, Second Edition]. Manning Publications Co. 2015.
+  Addison-Wesley Professional. 2002.
+- [[[JPwH]]] Christian Bauer & Gavin King. https://www.manning.com/books/java-persistence-with-hibernate-second-edition[Java Persistence with Hibernate, Second Edition]. Manning. 2015.

documentation/src/main/asciidoc/userguide/chapters/domain/basic_types.adoc

@@ -187,7 +187,7 @@ The `@Column` annotation defines other mapping information as well. See its Java
 
 We said before that a Hibernate type is not a Java type, nor an SQL type, but that it understands both and performs the marshalling between them.
 But looking at the basic type mappings from the previous examples,
-how did Hibernate know to use its `org.hibernate.type.StringType` for mapping for `java.lang.String` attributes,
+how did Hibernate know to use its `org.hibernate.type.StringType` for mapping `java.lang.String` attributes,
 or its `org.hibernate.type.IntegerType` for mapping `java.lang.Integer` attributes?
 
 The answer lies in a service inside Hibernate called the `org.hibernate.type.BasicTypeRegistry`, which essentially maintains a map of `org.hibernate.type.BasicType` (an `org.hibernate.type.Type` specialization) instances keyed by a name.

documentation/src/main/asciidoc/userguide/chapters/domain/naming.adoc

@@ -25,7 +25,7 @@ Also, the NamingStrategy contract was often not flexible enough to properly appl
 "rule", either because the API lacked the information to decide or because the API was honestly
 not well defined as it grew.
 
-Due to these limitation, `org.hibernate.cfg.NamingStrategy` has been deprecated
+Due to these limitations, `org.hibernate.cfg.NamingStrategy` has been deprecated
 in favor of ImplicitNamingStrategy and PhysicalNamingStrategy.
 ====
 
@@ -89,7 +89,7 @@ into the mapping via explicit names.
 
 While the purpose of an ImplicitNamingStrategy is to determine that an attribute named `accountNumber` maps to
 a logical column name of `accountNumber` when not explicitly specified, the purpose of a PhysicalNamingStrategy
-would be, for example, to say that the physical column name should instead be abbreviated `acct_num`.
+would be, for example, to say that the physical column name should instead be abbreviated to `acct_num`.
 
 [NOTE]
 ====

documentation/src/main/asciidoc/userguide/chapters/osgi/OSGi.adoc

@@ -33,7 +33,7 @@ Also, note that the features are heavily tested against Karaf 3.0.3 as a part of
 However, they'll likely work on other versions as well.
 
 hibernate-osgi, theoretically, supports a variety of OSGi containers, such as Equinox.
-In that case, please use `features.xm` as a reference for necessary bundles to activate and their correct ordering.
+In that case, please use `features.xml` as a reference for necessary bundles to activate and their correct ordering.
 However, note that Karaf starts a number of bundles automatically, several of which would need to be installed manually on alternatives.
 
 === QuickStarts/Demos

documentation/src/test/java/org/hibernate/userguide/mapping/basic/BitSetUserType.java

@@ -21,7 +21,7 @@ import org.jboss.logging.Logger;
 //tag::basic-custom-type-BitSetUserType-example[]
 public class BitSetUserType implements UserType {
 
-	public static final BitSetUserType INSTANCE = new BitSetUserType();
+    public static final BitSetUserType INSTANCE = new BitSetUserType();
 
     private static final Logger log = Logger.getLogger( BitSetUserType.class );