From a098396551a0c5152ccd755e79271aeb0aed1a53 Mon Sep 17 00:00:00 2001
From: Radoslaw Adamiak <radoslaw.adamiak@oviva.com>
Date: Wed, 9 Nov 2022 13:24:36 +0100
Subject: [PATCH] Fix quarkus.qute.strict-rendering config property name in
 documentation

---
 .../main/java/io/quarkus/qute/runtime/QuteRuntimeConfig.java    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/extensions/qute/runtime/src/main/java/io/quarkus/qute/runtime/QuteRuntimeConfig.java b/extensions/qute/runtime/src/main/java/io/quarkus/qute/runtime/QuteRuntimeConfig.java
index 18e2bc5622941..cb679eed25e32 100644
--- a/extensions/qute/runtime/src/main/java/io/quarkus/qute/runtime/QuteRuntimeConfig.java
+++ b/extensions/qute/runtime/src/main/java/io/quarkus/qute/runtime/QuteRuntimeConfig.java
@@ -14,7 +14,7 @@ public class QuteRuntimeConfig {
 
     /**
      * The strategy used when a standalone expression evaluates to a "not found" value at runtime and
-     * the {@code io.quarkus.qute.strict-rendering} config property is set to {@code false}
+     * the {@code quarkus.qute.strict-rendering} config property is set to {@code false}
      * <p>
      * This strategy is never used when evaluating section parameters, e.g. <code>{#if foo.name}</code>. In such case, it's the
      * responsibility of the section to handle this situation appropriately.