From 596a384c973dfb551bfb0c7099ae7b91df60aa77 Mon Sep 17 00:00:00 2001
From: Igor Santos <532299+igorsantos07@users.noreply.github.com>
Date: Thu, 15 Feb 2024 07:42:14 -0300
Subject: [PATCH] Explicit the version where script-aliases was included
 (#11847)

Since this was included in a minor version, it's nice to tell the user if this feature is available on the version they're running or if they need to upgrade. If it's not available, the only hint (besides the missing aliases on `composer list`) is the mild complaint at `composer validate`.
---
 doc/articles/scripts.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/articles/scripts.md b/doc/articles/scripts.md
index b7339cbc5..ec4004ebc 100644
--- a/doc/articles/scripts.md
+++ b/doc/articles/scripts.md
@@ -425,7 +425,7 @@ To set an environment variable in a cross-platform way, you can use `@putenv`:
 }
 ```
 
-## Custom descriptions.
+## Custom descriptions
 
 You can set custom script descriptions with the following in your `composer.json`:
 
@@ -442,9 +442,9 @@ describe what the scripts do when the command is run.
 
 > **Note:** You can only set custom descriptions of custom commands.
 
-## Custom aliases.
+## Custom aliases
 
-You can set custom script aliases with the following in your `composer.json`:
+As of Composer 2.7, you can set custom script aliases with the following in your `composer.json`:
 
 ```json
 {