(struts-site) branch asf-staging updated: Updates stage by Jenkins

[git-site-role]

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

asf-gitbox-commits pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/struts-site.git


The following commit(s) were added to refs/heads/asf-staging by this push:
     new 2e025cc4bb Updates stage by Jenkins
2e025cc4bb is described below

commit 2e025cc4bbcad07c5e0471373d650d3f922b79c1
Author: jenkins <bui...@apache.org>
AuthorDate: Sat Oct 10 12:52:11 2026 +0000

    Updates stage by Jenkins
---
 content/core-developers/wildcard-mappings.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/core-developers/wildcard-mappings.html 
b/content/core-developers/wildcard-mappings.html
index 8caf6db748..1e4cf249c6 100644
--- a/content/core-developers/wildcard-mappings.html
+++ b/content/core-developers/wildcard-mappings.html
@@ -185,7 +185,7 @@ replacing <code class="language-plaintext 
highlighter-rouge">{1}</code>. For the
 the new values.</p>
 
 <p>Mappings are matched against the request in the order they appear in the 
framework’s configuration file. If more than 
-one pattern matches <strong>the last one wins</strong>, so less specific 
patterns must appear before more specific ones. However, 
+one pattern matches <strong>the first one wins</strong>, so more specific 
patterns must appear before less specific ones. However, 
 if the request URL can be matched against a path without any wildcards in it, 
no wildcard matching is performed 
 and order is not important. Also, note that wildcards are not greedy, meaning 
they only match until the first 
 occurrence of the following string pattern.  For example, consider the 
following mapping:</p>