Copilot instructions and more fixes

Author: samdark

.github/copilot-instructions.md

@@ -0,0 +1,2 @@
+- Edits are permitted only in `cookbook/en`, `guide/en` and `.md` files in root directory.
+- Conform to `014-docs.md` except translations part.

001-yii-values.md

@@ -32,7 +32,7 @@ We seek a balance between flexibility, discipline and simplicity that meets comm
 
 We prefer practice to theory. For example:
 
-- Solutions for known use cases should avoid excess complexity by providing only needed flexibility.
+- Solutions for known use cases should avoid excess complexity by providing only necessary flexibility.
 - Standard implementations should take practical use into account.
 - Experience is at least as useful as theory in guiding design.
 - Context is critical in determining appropriateness.
@@ -43,7 +43,7 @@ This value guides technical decisions as well as community activity.
 Consideration of how software features help users should guide development.
 Community-wise, we value any helpful contribution, be it a pull request or an answer in the forum.
 
-When the other principles could conflict, we choose a solution that's more helpful to the community.
+When the other principles conflict, we choose a solution that's more helpful to the community.
 
 ### Be simple
 
@@ -57,7 +57,7 @@ Solutions should be simple and expressive:
 
 We prefer explicit, obvious solutions and code. Solutions should clearly express exactly what they do. For example:
 
-- A straightforward solution is better than an abstract one unless the abstraction has practical purpose.
+- A straightforward solution is better than an abstract one unless the abstraction has a practical purpose.
 - Loud fails are better than silent fails or masking errors.
 - Explicit casts are better than PHP type juggling, type hints are good.
 - No magic unless necessary.

014-docs.md

@@ -25,20 +25,28 @@ The guide should follow [Micosoft style guide](https://learn.microsoft.com/en-us
 
 ### Translation
 
-The definitive guide uses [po4a](https://github.com/mquinson/po4a) in Github Action for translations.  
+The definitive guide uses [po4a](https://github.com/mquinson/po4a) in GitHub Action for translations.  
+
 Translation algorithm:
-- Install an application for working with `.po` translation files. For example, [Poedit](https://poedit.net/), [Lokalize](https://apps.kde.org/ru/lokalize/), [Gtranslator](https://wiki.gnome.org/Apps/Gtranslator) or another.
-- Find folder with the name of the file you want to translate in `/guide/po`. Note that if the source file is in a subfolder, the subfolder name is appended to the folder and separated by an underscore, for example: for translating `guide/en/concept/aliases.md` file find `guide/po/concept_aliases.md` folder.
-- Open the file with the `.po` extension in `Poedit` from the folder with the desired localization, for example `guide/po/intro_what-is-yii.md/ru/intro_what-is-yii.md.ru.po`. If there is no localization yet, create an issue.
+
+- Install an application for working with `.po` translation files. For example, [Poedit](https://poedit.net/), [Lokalize](https://apps.kde.org/ru/lokalize/),
+  [Gtranslator](https://wiki.gnome.org/Apps/Gtranslator) or another.
+- Find folder with the name of the file you want to translate in `/guide/po`. Note that if the source file
+  is in a subfolder, the subfolder name is appended to the folder and separated by an underscore, for example,
+  for translating `guide/en/concept/aliases.md` file find `guide/po/concept_aliases.md` folder.
+- Open the file with the `.po` extension in `Poedit` from the folder with the desired localization,
+  for example `guide/po/intro_what-is-yii.md/ru/intro_what-is-yii.md.ru.po`. If there is no localization yet,
+  create an issue.
 - Translate necessary strings and push the changes
-- Open pull request to main repository
+- Open a pull request to the main repository
 
 > [!CAUTION]
 > Do not change the translation in files in `/guide/{lang}` manually.
 
-If you have changed English documentation:
-- Open pull request to main repository
-- Pull updated branch after successful completion of workflow `Update docs translation` in Github Action
+If you have changed English and want to update translations:
+
+- Open a pull request to the main repository
+- Pull updated branch after successful completion of workflow `Update docs translation` in GitHub Action
 - Update translation in `.po` files by `Poedit`
 - Push changes
 

016-security-workflow.md

@@ -39,4 +39,4 @@ It usually takes several days.
 - Merge the patch pull request right before tagging the next package release.
 - Publish security advisory.
 - Add CVE to [FriendsOfPHP/security-advisories](https://github.com/FriendsOfPHP/security-advisories).
-  See [#488](https://github.com/FriendsOfPHP/security-advisories/pull/488) as example.
+  See [#488](https://github.com/FriendsOfPHP/security-advisories/pull/488) as an example.