(lucene-site) branch main updated: fix markdown in Lucene new update for 10.2.1

[ch...@apache.org]

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

chegar pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/lucene-site.git


The following commit(s) were added to refs/heads/main by this push:
     new 8b9f5cce2 fix markdown in Lucene new update for 10.2.1
8b9f5cce2 is described below

commit 8b9f5cce260aca094ba3a8162614fdc98be4d451
Author: ChrisHegarty <ch...@gmail.com>
AuthorDate: Thu May 1 14:07:12 2025 +0100

    fix markdown in Lucene new update for 10.2.1
---
 content/core/core_news/2025-05-01-2-0-available.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/core/core_news/2025-05-01-2-0-available.md b/content/core/core_news/2025-05-01-2-0-available.md
index ba329d17d..34657c389 100644
--- a/content/core/core_news/2025-05-01-2-0-available.md
+++ b/content/core/core_news/2025-05-01-2-0-available.md
@@ -15,10 +15,10 @@ This patch release contains bug fixes that are highlighted below. The release is
 
 #### Bug fixes
 
-* Fix DISIDocIdStream::count so that it does not try to count beyond max.
-* Correct TermOrdValComparator competitive iterator so that it forces sparse field iteration to be at least scoring window baseline when doing intoBitSet.
-* Provide better impacts for fields indexed with IndexOptions.DOCS
-* Fixed lead cost computations for bulk scorers of conjunctive queries that mix MUST and FILTER clauses, and disjunctive queries that configure a minimum number of matching SHOULD clauses.
+ * Fix DISIDocIdStream::count so that it does not try to count beyond max.
+ * Correct TermOrdValComparator competitive iterator so that it forces sparse field iteration to be at least scoring window baseline when doing intoBitSet.
+ * Provide better impacts for fields indexed with IndexOptions.DOCS
+ * Fixed lead cost computations for bulk scorers of conjunctive queries that mix MUST and FILTER clauses, and disjunctive queries that configure a minimum number of matching SHOULD clauses.
 
 Further details of changes are available in the change log available at: