docs(security): update supported versions

Signed-off-by: Romain Lespinasse <[email protected]>

SECURITY.md

@@ -5,22 +5,22 @@
 | Version | Supported          | End of Support | Branch | Specific Tags |
 | ------- | ------------------ | -------------- | ------ | ------------- |
 | 4.x     | :white_check_mark: |                | v4.x   | v4            |
-| 3.x     | :white_check_mark: | 2024-01-31     | v3.x   | v3            |
+| 3.x     | :x:                | 2024-01-31     |        | v3.x, v3      |
 | 2.x     | :x:                | 2021-04-05     |        | v2.x, 2.2.0   |
 | 1.x     | :x:                | 2021-04-05     |        | v1.1.x, 1.2.0 |
 | 1.0.x   | :x:                | 2019-11-07     |        | 1.0.2         |
 
-A GitHub repository can used one of the available branches as action inside its workflows.
+A GitHub repository can use one of the available branches as an action inside its workflows.
 
 ### End of Life of a branch
 
-Since `2023-10-20`, when a new major version is release,
+Since `2023-10-20`, when a new major version is released,
 
-- The previous one will continue to receive security patches during a 3-months periods,
-- After the 3-month periods, the branch is deleted, only the tags remains.
+- The previous one will continue to receive security patches for 3 months,
+- After the 3 months, the branch is deleted, and only the tags remain.
 
 ## Reporting a Vulnerability
 
-You can report a Vulnerability by creating a [draft security advisory](https://github.com/rlespinasse/github-slug-action/security/advisories) in this project.
+In this project, you can report a Vulnerability by creating a [draft security advisory](https://github.com/rlespinasse/github-slug-action/security/advisories).
 
-If the vulnerability is confirm, a fix will be produce and the advisory will be publish.
+If the vulnerability is confirmed, a fix will be produced and the advisory will be published.