(solr) 03/03: Fix formatting of commit and optimize operation tags (#4740)

[ds...@apache.org]

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

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

commit 9d50dd31de1196d7024649623a7ca130c340e33a
Author: Eric Pugh <ep...@opensourceconnections.com>
AuthorDate: Sat Aug 15 14:11:37 2026 -0400

    Fix formatting of commit and optimize operation tags (#4740)
    
    (cherry picked from commit dd1ed4b711c869e89428fc01e76fbba8676359fc)
    (cherry picked from commit c4d82b652e3fc9ea0872d6636ef664da12c2c92b)
---
 .../modules/indexing-guide/pages/indexing-with-update-handlers.adoc   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/solr/solr-ref-guide/modules/indexing-guide/pages/indexing-with-update-handlers.adoc b/solr/solr-ref-guide/modules/indexing-guide/pages/indexing-with-update-handlers.adoc
index 44aa38a85a7..2530f73733a 100644
--- a/solr/solr-ref-guide/modules/indexing-guide/pages/indexing-with-update-handlers.adoc
+++ b/solr/solr-ref-guide/modules/indexing-guide/pages/indexing-with-update-handlers.adoc
@@ -135,7 +135,7 @@ Blocks until a new searcher is opened and registered as the main query searcher,
 +
 Merges segments that have more than 10% deleted docs, expunging the deleted documents in the process.
 Resulting segments will respect `maxMergedSegmentMB`.
-This option only applies in a `<commit> operation`.
+This option only applies in a `<commit>` operation.
 +
 WARNING: `expungeDeletes` is less expensive than optimize, but the same warnings apply.
 
@@ -148,7 +148,7 @@ WARNING: `expungeDeletes` is less expensive than optimize, but the same warnings
 +
 Makes a best effort attempt to merge the segments down to no more than this number of segments but does not guarantee that the goal will be achieved.
 Unless there is tangible evidence that optimizing to a small number of segments is beneficial, this parameter should be omitted and the default behavior accepted.
-This option only applies in a `<optimize` operation.
+This option only applies in a `<optimize>` operation.
 Default is unlimited, resulting segments respect the `maxMergedSegmentMB` setting.
 
 Here are examples of `<commit>` and `<optimize>` using optional attributes: