add more links to the Short Guide

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

@@ -1,6 +1,10 @@
 [[introduction]]
 == Introduction
 
+:persistence: https://jakarta.ee/specifications/persistence/3.2/jakarta-persistence-spec-3.2
+:data: https://jakarta.ee/specifications/data/1.0/jakarta-data-1.0
+
+
 Hibernate is usually described as a library that makes it easy to map Java classes to relational database tables.
 But this formulation does no justice to the central role played by the relational data itself.
 So a better description might be:
@@ -35,7 +39,7 @@ Developers often ask about the relationship between Hibernate and JPA, so let's
 [[hibernate-and-jpa]]
 === Hibernate and JPA
 
-Hibernate was the inspiration behind the _Java_ (now _Jakarta_) _Persistence API_, or JPA, and includes a complete implementation of the latest revision of this specification.
+Hibernate was the inspiration behind the _Java_ (now _Jakarta_) _Persistence API_, or JPA, and includes a complete implementation of the latest revision of link:{persistence}[this specification].
 
 .The early history of Hibernate and JPA
 ****
@@ -669,7 +673,7 @@ Alternatively, if CDI isn't available, we may directly instantiate the generated
 
 [TIP]
 ====
-The Jakarta Data specification now formalizes this approach using standard annotations, and our implementation of this specification, Hibernate Data Repositories, is built into <<generator,Hibernate Processor>>.
+The link:{data}[Jakarta Data specification] now formalizes this approach using standard annotations, and our implementation of this specification, Hibernate Data Repositories, is built into <<generator,Hibernate Processor>>.
 You probably already have it available in your program.
 
 Unlike other repository frameworks, Hibernate Data Repositories offers something that plain JPA simply doesn’t have: full compile-time type safety for your queries. To learn more, please refer to link:{doc-data-repositories-url}[Introducing Hibernate Data Repositories].

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

@@ -1,19 +1,21 @@
 [[preface]]
 == Preface
 
+:persistence: https://jakarta.ee/specifications/persistence/3.2/jakarta-persistence-spec-3.2
+:data: https://jakarta.ee/specifications/data/1.0/jakarta-data-1.0
+
 Hibernate 6 was a major redesign of the world's most popular and feature-rich ORM solution.
 The redesign touched almost every subsystem of Hibernate, including the APIs, mapping annotations, and the query language.
 This new Hibernate was suddenly more powerful, more robust, more portable, and more type safe.
 
-Hibernate 7 builds on this foundation, adds support for JPA 3.2, and introduces Hibernate Data Repositories, an implementation of the Jakarta Data specification.
+Hibernate 7 builds on this foundation, adds support for link:{persistence}[JPA 3.2], and introduces https://hibernate.org/repositories/[Hibernate Data Repositories], an implementation of the link:{data}[Jakarta Data specification].
 Taken together, these enhancements yield a level of compile-time type safety--and resulting developer productivity--which was previously impossible.
 Hibernate Data Repositories offers truly seamless integration of the ORM solution with the persistence layer, obsoleting older add-on repository frameworks.
 
-Hibernate and Hibernate Reactive are core components of Quarkus 3, the most exciting new environment for cloud-native development in Java, and Hibernate remains the persistence solution of choice for almost every major Java framework or server.
+Hibernate ORM and https://hibernate.org/reactive/[Hibernate Reactive] are core components of https://quarkus.io[Quarkus 3], the most exciting new environment for cloud-native development in Java, and Hibernate remains the persistence solution of choice for almost every major Java framework or server.
 
 Unfortunately, the changes in Hibernate 6 also obsoleted much of the information about Hibernate that's available in books, in blog posts, and on stackoverflow.
 
-
 This guide is an up-to-date, high-level discussion of the current feature set and recommended usage.
 It does not attempt to cover every feature and should be used in conjunction with other documentation:
 

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

@@ -9,10 +9,10 @@ We've actually already seen its handiwork in the code examples <<main-hibernate,
 .Hibernate Processor
 ****
 
-:generator: https://hibernate.org/orm/tooling/
+:generator: https://hibernate.org/orm/processor/
 :generator-guide: {doc-user-guide-url}#tooling-modelgen
 
-{generator}[Hibernate Processor], the annotation processor formerly known as the Metamodel Generator, began its life as a code generator for what JPA calls a _static metamodel_.
+{generator}[Hibernate Processor], the annotation processor formerly known as the Metamodel Generator, began its life as a code generator for what JPA calls a https://jakarta.ee/specifications/persistence/3.2/jakarta-persistence-spec-3.2#a6072[_static metamodel_].
 That is, it produces a typed model of the persistent classes in our program, giving us a type safe way to refer to their attributes in Java code.
 In particular, it lets us specify <<entity-graph,entity graphs>> and <<criteria-queries,criteria queries>> in a completely type-safe way.