HV-2143 Adjust image layout

documentation/src/main/asciidoc/_ch08.adoc

@@ -22,7 +22,7 @@ _validation.xml_ has to adhere.
 
 [[image-validation-configuration]]
 .Validation configuration schema
-image::validation-configuration-2.0.png[validation-configuration-2.0.xsd]
+image::validation-configuration-2.0.png[validation-configuration-2.0.xsd,align="center"]
 
 <<example-validation-xml>>
 shows the several configuration options of _validation.xml_. All settings are optional and the same
@@ -81,7 +81,7 @@ constraint-mapping in _validation.xml_.
 
 [[image-mapping-configuration]]
 .Validation mapping schema
-image::validation-mapping-2.0.png[validation-mapping-2.0.xsd]
+image::validation-mapping-2.0.png[validation-mapping-2.0.xsd,align="center"]
 
 <<example-constraints-car>> shows how the classes +Car+ and +RentalCar+ from <<example-car>> resp.
 <<example-rental-car>> could be mapped in XML.

documentation/src/main/asciidoc/_ch13.adoc

@@ -195,7 +195,7 @@ hibernate-validator-annotation-processor-{hvVersion}.jar
 You now should see any annotation problems as regular error markers within the editor and in the
 "Problem" view:
 
-image::annotation_processor_eclipse.png[]
+image::annotation_processor_eclipse.png[align="center"]
 
 [[validator-annotationprocessor-idea]]
 ===== IntelliJ IDEA
@@ -213,7 +213,7 @@ to the "Annotation Processors" list
 
 Rebuilding your project then should show any erroneous constraint annotations:
 
-image::annotation_processor_intellij.png[]
+image::annotation_processor_intellij.png[align="center"]
 
 [[validator-annotationprocessor-netbeans]]
 ===== NetBeans
@@ -229,7 +229,7 @@ org.hibernate.validator.ap.ConstraintValidationProcessor
 
 Any constraint annotation problems will then be marked directly within the editor:
 
-image::annotation_processor_netbeans.png[]
+image::annotation_processor_netbeans.png[align="center"]
 
 [[validator-annotationprocessor-known-issues]]
 === Known issues

documentation/src/main/asciidoc/_pr01.adoc

@@ -9,15 +9,15 @@ which is time consuming and error-prone. To avoid duplication of these validatio
 bundle validation logic directly into the domain model, cluttering domain classes with validation
 code which is really metadata about the class itself.
 
-image::application-layers.png[]
+image::application-layers.png[align="center"]
 
 Jakarta Validation {bvVersion} defines a metadata model and API for entity and method validation.
 The default metadata source are annotations, with the ability to override and extend the meta-data
 through the use of XML. The API is not tied to a specific application tier nor programming model. It
 is specifically not tied to either web or persistence tier, and is available for both server-side
 application programming, as well as rich client Swing application developers.
 
-image::application-layers2.png[]
+image::application-layers2.png[align="center"]
 
 Hibernate Validator is the reference implementation of Jakarta Validation. The implementation itself as
 well as the Jakarta Validation API and TCK are all provided and distributed under the

pom.xml

@@ -224,7 +224,7 @@
         <!-- Asciidoctor -->
 
         <version.asciidoctor.plugin>3.2.0</version.asciidoctor.plugin>
-        <version.org.hibernate.infra.hibernate-asciidoctor-theme>6.0.2.Final</version.org.hibernate.infra.hibernate-asciidoctor-theme>
+        <version.org.hibernate.infra.hibernate-asciidoctor-theme>6.0.4.Final</version.org.hibernate.infra.hibernate-asciidoctor-theme>
         <version.org.hibernate.infra.hibernate-asciidoctor-extensions>3.2.0.Final</version.org.hibernate.infra.hibernate-asciidoctor-extensions>
         <version.org.asciidoctor.asciidoctorj>3.0.0</version.org.asciidoctor.asciidoctorj>
         <version.org.asciidoctor.asciidoctorj-pdf>2.3.20</version.org.asciidoctor.asciidoctorj-pdf>