From e6e51132e3d9eb44ff978e63f47d3ef8fab4acd2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Yoann=20Rodi=C3=A8re?= <yoann@hibernate.org>
Date: Mon, 4 Jul 2022 09:31:23 +0200
Subject: [PATCH] HSEARCH-4319 Fix typo in documentation

---
 .../src/main/asciidoc/reference/backend-lucene.asciidoc         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/src/main/asciidoc/reference/backend-lucene.asciidoc b/documentation/src/main/asciidoc/reference/backend-lucene.asciidoc
index ebc4a85bd0e..14444706803 100644
--- a/documentation/src/main/asciidoc/reference/backend-lucene.asciidoc
+++ b/documentation/src/main/asciidoc/reference/backend-lucene.asciidoc
@@ -378,7 +378,7 @@ but Hibernate Search maintains such a schema in memory,
 in order to remember which predicates/projections/sorts can be applied to each field.
 
 For the most part, the schema is inferred from
-<<mappingthe mapping configured through Hibernate Search's mapping APIs>>,
+<<mapping,the mapping configured through Hibernate Search's mapping APIs>>,
 which are generic and independent of Lucene.
 
 Aspects that are specific to the Lucene backend are explained in this section.