(maven-site) 01/01: improve settings doc

[hb...@apache.org]

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

hboutemy pushed a commit to branch improve-settings
in repository https://gitbox.apache.org/repos/asf/maven-site.git

commit bf04760c0cf4a273a5fa1299a63d14847136f81e
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Sun Oct 18 22:05:08 2026 +0200

    improve settings doc
---
 content/markdown/docs/3.10.0/release-notes.md             |  2 +-
 .../guides/mini/guide-deployment-security-settings.md     |  2 +-
 content/markdown/settings.md                              | 15 +++++++--------
 content/site.xml                                          |  7 ++++---
 4 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/content/markdown/docs/3.10.0/release-notes.md b/content/markdown/docs/3.10.0/release-notes.md
index 7639b1de..bb65b097 100644
--- a/content/markdown/docs/3.10.0/release-notes.md
+++ b/content/markdown/docs/3.10.0/release-notes.md
@@ -53,7 +53,7 @@ Maven 3.10.0 requires Java 8 or above to run, same as the Maven 3.9.x lineage.
 - new CLI options for fine-grained update policy control: `-UA` (force artifact updates only), `-UM` (force metadata
   updates only), `--artifacts-update-policy=<policy>`, `--metadata-update-policy=<policy>`
 - a `<server>` in `settings.xml` can declare `<aliases>`, so that one set of credentials serves several server ids
-  ([#7757](https://github.com/apache/maven/issues/7757))
+  (see [Introduction to Settings](/settings.html))
 - a `<server>` in `settings.xml` can declare `<repositoryOrigins>`, to state explicitly which repository origins its
   credentials may be used with
 - the reactor summary is complete again: every module is listed, including the skipped ones, and failures are reported
diff --git a/content/markdown/guides/mini/guide-deployment-security-settings.md b/content/markdown/guides/mini/guide-deployment-security-settings.md
index 8522df26..a9c736a9 100644
--- a/content/markdown/guides/mini/guide-deployment-security-settings.md
+++ b/content/markdown/guides/mini/guide-deployment-security-settings.md
@@ -47,4 +47,4 @@ Which settings are required will depend on the type of repository you are deploy
 
 To encrypt passwords in these sections, refer to [Encryption Settings](./guide-encryption.html).
 
-**Note**: The settings descriptor documentation can be found on the [Maven Local Settings Model Website](../../maven-settings/settings.html).
+**Note**: The settings descriptor documentation can be found on the [Maven Settings Descriptor Model](/ref/current/maven-settings/settings.html).
diff --git a/content/markdown/settings.md b/content/markdown/settings.md
index 9cd2ec1e..6f75223f 100644
--- a/content/markdown/settings.md
+++ b/content/markdown/settings.md
@@ -196,24 +196,23 @@ whole `server` element.
 </settings>
 ```
 
-- **aliases**: For each `alias`, Maven generates an additional server
+- **aliases**: For each `alias`, Maven creates an additional `server`
   entry with the same configuration as the original one, but with the
-  `id` replaced by the alias and with an empty aliases list.
+  `id` replaced by the alias and with an empty `aliases` list.
   In the example above, the servers `company-releases`,
-  `company-snapshots` and `company-mirror` all use the same credentials.
+  `company-snapshots` and `company-mirror` are available at runtime, all use the same credentials.
 
-The additional servers are created in memory when the settings are built,
+The additional servers are created in memory when the effective settings are built,
 so they are visible to Maven and plugins like any other server
-declared in `settings.xml`.
+declared in `settings.xml`: you can see them with `mvn help:effective-settings`.
 
 An alias must not be empty, and it should be unique across all server IDs
 and aliases. Otherwise Maven reports a warning.
 
 #### Password Encryption
 
-A new feature - server password and passphrase encryption has been added
-to 2.1.0+. See details [on this
-page](./guides/mini/guide-encryption.html)
+Since Maven 2.1.0, server password and passphrase encryption is available and strongly encouraged:
+See details on [Guide to Password Encryption](./guides/mini/guide-encryption.html).
 
 ### Mirrors
 
diff --git a/content/site.xml b/content/site.xml
index d96ecea1..92857db1 100644
--- a/content/site.xml
+++ b/content/site.xml
@@ -110,9 +110,10 @@ under the License.
             <item name="Large Scale Centralized Deployments"
                   href="/guides/mini/guide-large-scale-centralized-deployments.html"/>
             <item name="Mirror Settings" href="/guides/mini/guide-mirror-settings.html"/>
-            <item name="Deployment and Security Settings" href="/guides/mini/guide-deployment-security-settings.html"/>
-            <item name="Encrypting Passwords (Maven 3)" href="/guides/mini/guide-encryption.html"/>
-            <item name="Encrypting Passwords (Maven 4)" href="/guides/mini/guide-encryption-4.html"/>
+            <item name="Deployment and Security Settings" href="/guides/mini/guide-deployment-security-settings.html">
+              <item name="Encrypting Passwords (Maven 3)" href="/guides/mini/guide-encryption.html"/>
+              <item name="Encrypting Passwords (Maven 4)" href="/guides/mini/guide-encryption-4.html"/>
+            </item>
             <item name="Using Proxies" href="/guides/mini/guide-proxies.html"/>
             <item name="Authenticated HTTPS" href="/guides/mini/guide-repository-ssl.html"/>
             <item name="Resolver Transport" href="/guides/mini/guide-resolver-transport.html"/>