insure -> ensure

spec/src/main/asciidoc/ch03-entity-operations.adoc

@@ -470,7 +470,7 @@ required, the application must not use lazy loading.
 ==== Managed Instances
 
 It is the responsibility of the application
-to insure that an instance is managed in only a single persistence
+to ensure that an instance is managed in only a single persistence
 context. The behavior is undefined if the same Java instance is made
 managed in more than one persistence context.
 

spec/src/main/asciidoc/ch06-criteria-api.adoc

@@ -1819,7 +1819,7 @@ query object has been created from it. The modification of the
 have any impact on the already created executable query object. If the
 modified `CriteriaQuery`, `CriteriaUpdate`, or `CriteriaDelete` object
 is passed to the `createQuery` method, the persistence provider must
-insure that a new executable query object is created and returned that
+ensure that a new executable query object is created and returned that
 reflects the semantics of the changed query definition.
 
 `CriteriaQuery`, `CriteriaUpdate`, and

spec/src/main/asciidoc/ch08-entity-packaging.adoc

@@ -73,7 +73,7 @@ may be using different persistence units), the referenced class is the same
 identical class.
 
 In Java SE environments, the metadata mapping files, jar files, and classes
-described in the following sections can be used. To insure the portability
+described in the following sections can be used. To ensure the portability
 of a Java SE application, it is necessary to explicitly list the managed
 persistence classes included in the persistence unit using the `class`
 element of the `persistence.xml` file. See <<a12305>>.
@@ -463,7 +463,7 @@ the mapping annotation defaults. The `class` element is used to list
 a managed persistence class.
 
 In Java SE environments, an explicit list of all managed persistence
-class names must be specified to insure portability. Portable Java SE
+class names must be specified to ensure portability. Portable Java SE
 applications should not rely on the other mechanisms described here to
 determine the managed persistence classes of a persistence unit. In
 Java SE environments, a persistence provider may require that the set

spec/src/main/asciidoc/ch09-container-provider-contracts.adoc

@@ -807,7 +807,7 @@ the entity is present in the environment._
 don't need to access an attribute reference to determine its load state,
 and can determine if the entity has been provided by them._
 * _By first querying all providers using
-bytecode enhancement, it is insured that no attribute will be loaded by
+bytecode enhancement, it is ensured that no attribute will be loaded by
 side effect._
 * _Proxy-based providers do need to access an
 attribute reference to determine load state, but will not trigger

spec/src/main/asciidoc/ch11-metadata-for-or-mapping.adoc

@@ -13,7 +13,7 @@ schema that corresponds to the application domain model are dependent
 upon the mappings expressed by means of the object/relational mapping
 metadata. The implementation of this specification must assume this
 application dependency upon the object/relational mapping metadata and
-insure that the semantics and requirements expressed by that mapping are
+ensure that the semantics and requirements expressed by that mapping are
 observed.
 
 The use of object/relational mapping metadata