(solr) branch main updated: SOLR-18464: Fix three Antora build warnings in the ref guide (#4922)

[ep...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

epugh pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr.git


The following commit(s) were added to refs/heads/main by this push:
     new 4811a8d3447 SOLR-18464: Fix three Antora build warnings in the ref guide (#4922)
4811a8d3447 is described below

commit 4811a8d3447197720a642b59428b2c51b7b9be8d
Author: Serhiy Bzhezytskyy <me...@serhiy-bzhezytskyy.com>
AuthorDate: Tue Sep 22 11:52:31 2026 +0300

    SOLR-18464: Fix three Antora build warnings in the ref guide (#4922)
---
 .../modules/configuration-guide/pages/configsets-api.adoc         | 4 ++--
 .../deployment-guide/pages/rule-based-authorization-plugin.adoc   | 2 +-
 .../indexing-guide/pages/document-enrichment-with-llms.adoc       | 8 ++++----
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/solr/solr-ref-guide/modules/configuration-guide/pages/configsets-api.adoc b/solr/solr-ref-guide/modules/configuration-guide/pages/configsets-api.adoc
index a8cfecfe430..81d5ff78646 100644
--- a/solr/solr-ref-guide/modules/configuration-guide/pages/configsets-api.adoc
+++ b/solr/solr-ref-guide/modules/configuration-guide/pages/configsets-api.adoc
@@ -258,7 +258,7 @@ V2 API::
 +
 ====
 With the v2 API, the file path is part of the URL path.
-Use a `PUT` request to `/api/configsets/{configSetName}/files/{filePath}`:
+Use a `PUT` request to `/api/configsets/\{configSetName}/files/\{filePath}`:
 
 
 [source,bash]
@@ -327,7 +327,7 @@ V2 API::
 +
 ====
 With the v2 API, the file path is part of the URL path.
-Use a `GET` request to `/api/configsets/{configSetName}/files/{filePath}`:
+Use a `GET` request to `/api/configsets/\{configSetName}/files/\{filePath}`:
 
 [source,bash]
 ----
diff --git a/solr/solr-ref-guide/modules/deployment-guide/pages/rule-based-authorization-plugin.adoc b/solr/solr-ref-guide/modules/deployment-guide/pages/rule-based-authorization-plugin.adoc
index c243186a928..0d1e0f5c482 100644
--- a/solr/solr-ref-guide/modules/deployment-guide/pages/rule-based-authorization-plugin.adoc
+++ b/solr/solr-ref-guide/modules/deployment-guide/pages/rule-based-authorization-plugin.adoc
@@ -405,7 +405,7 @@ If edit permissions should only be applied to specific collections, a custom per
 Specifically, the following actions of the Collections API would be allowed:
 
 +
-[.lowpadding,cols="1,1,1",frame=none,grid=none,stripes=none]
+[.lowpadding,cols="1,1,1,1",frame=none,grid=none,stripes=none]
 |===
 | CREATE
 | RELOAD
diff --git a/solr/solr-ref-guide/modules/indexing-guide/pages/document-enrichment-with-llms.adoc b/solr/solr-ref-guide/modules/indexing-guide/pages/document-enrichment-with-llms.adoc
index 600268187ae..a8b0ac1d257 100644
--- a/solr/solr-ref-guide/modules/indexing-guide/pages/document-enrichment-with-llms.adoc
+++ b/solr/solr-ref-guide/modules/indexing-guide/pages/document-enrichment-with-llms.adoc
@@ -131,7 +131,7 @@ s|Exactly one of these parameters is required |Default: none
 +
 Two different ways to define a prompt are available: one directly in the solrconfig and one through a dedicated file.
 Either way, the content of the prompt _must_ contain a special token for each `inputField` declared, that are the
-`fieldName` surrounded by curly brackets (e.g., `{string_field}`, in the example below). Solr will throw an error if
+`fieldName` surrounded by curly brackets (e.g., `\{string_field}`, in the example below). Solr will throw an error if
 the parameters are not properly defined.
 +
 These parameters can be defined in one of the following ways:
@@ -144,7 +144,7 @@ These parameters can be defined in one of the following ways:
   <processor class="solr.languagemodels.update.processor.factory.DocumentEnrichmentUpdateProcessorFactory">
    <str name="inputField">string_field</str>
    <str name="outputField">summary</str>
-   <str name="prompt">Summarize this content: {string_field}</str>
+   <str name="prompt">Summarize this content: \{string_field}</str>
    <str name="model">model-name</str>
   </processor>
   <processor class="solr.RunUpdateProcessorFactory"/>
@@ -441,7 +441,7 @@ excluding the `DocumentEnrichmentUpdateProcessor` (let's call it 'no-enrichment'
   <processor class="solr.languagemodels.update.processor.factory.DocumentEnrichmentUpdateProcessorFactory">
    <str name="inputField">string_field</str>
    <str name="outputField">summary</str>
-   <str name="prompt">Summarize this content: {string_field}</str>
+   <str name="prompt">Summarize this content: \{string_field}</str>
    <str name="model">model-name</str>
   </processor>
   <processor class="solr.RunUpdateProcessorFactory"/>
@@ -485,7 +485,7 @@ You still define two chains, but this time the 'enrichment' one only includes th
   <processor class="solr.languagemodels.update.processor.factory.DocumentEnrichmentUpdateProcessorFactory">
    <str name="inputField">string_field</str>
    <str name="outputField">summary</str>
-   <str name="prompt">Summarize this content: {string_field}</str>
+   <str name="prompt">Summarize this content: \{string_field}</str>
    <str name="model">model-name</str>
   </processor>
   <processor class="solr.RunUpdateProcessorFactory"/>