docs: improve details about contributions

Signed-off-by: Pierre-Yves Lapersonne <[email protected]>

Author: pylapp

.github/CONTRIBUTING.md

@@ -15,14 +15,16 @@
 
 Looking to contribute something OUDS iOS? **Here's how you can help.**
 
-Please take a moment to review this document in order to make the contribution process easy for everyone involved.
+> [!TIP]
+> Please take a moment to review this document in order to make the contribution process easy for everyone involved.
 
-Following these guidelines helps to communicate that you respect the time of the developers managing and developing this Open Source project.
-In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
+> [!IMPORTANT]
+> Following these guidelines helps to communicate that you respect the time of the developers managing and developing this Open Source project.
+> In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
 
-You should also have a look on the wiki if you are looking for information about how the project is managed, the releases and tests done, and how to do some actions.
-[The wiki define the way to work anyone must agree](https://github.com/Orange-OpenSource/ouds-ios/wiki).
-[The Code of Conduct](https://github.com/Orange-OpenSource/ouds-ios-design-system-toolbox/blob/develop/.github/CODE_OF_CONDUCT.md) defines how we should interact together.
+You should also have a look on the wiki if you are looking for information about how the project is managed, the releases and tests done, and how to do some actions:
+- [The wiki define the way to work anyone must agree](https://github.com/Orange-OpenSource/ouds-ios/wiki).
+- [The Code of Conduct](https://github.com/Orange-OpenSource/ouds-ios-design-system-toolbox/blob/develop/.github/CODE_OF_CONDUCT.md) defines how we should interact together.
 
 ## Using the Issue Tracker
 
@@ -40,7 +42,7 @@ The OUDS project contains two repositories: one for the [Swift Package library](
 
 Because today we want to have [one board for both repositories](https://github.com/orgs/Orange-OpenSource/projects/40/views/4), there is no board no issues tracker for this app GitHub project, and anything is centralized in the library GitHub project.
 
-Thus, if you want to refer to an issue in the other project in commits, CHANGELOG, issues, pull requests or discussions, you msut use the [GitHub dedicated convention](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls) about issues references.
+Thus, if you want to refer to an issue in the other project in commits, CHANGELOG, issues, pull requests or discussions, you must use the [GitHub dedicated convention](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls) about issues references.
 In few words, if you are on an issue n°42 in [ouds-ios](https://github.com/Orange-OpenSource/ouds-ios), do not mention `#42` in your messages, but `Orange-OpenSource/ouds-iOS#42`.
 
 ## Using the Discussion Tracker
@@ -106,7 +108,10 @@ Good pull requests (patches, improvements, new features) are a fantastic help. T
 
 Please adhere to the [coding guidelines](#code-guidelines) used throughout the project (indentation, accurate comments, etc.) and any other requirements (such as test coverage).
 
-Adhering to the following process is the best way to get your work included in the project:
+Adhering to the following process is the best way to get your work included in the project.
+
+> [!TIP]
+> Of course you can use GUI tools if your are not used to CLI
 
 1. [Fork](https://help.github.com/articles/fork-a-repo/) the project, clone your fork, and configure the remotes:
 
@@ -153,7 +158,7 @@ Adhering to the following process is the best way to get your work included in t
 
 Note that a ruleset based [on task-list-completed tool](https://github.com/marketplace/task-list-completed) is applied on `develop` branch: if any prerequisites are not futfilled in the pull request ticket the merge won't be done. 
 
-8. If your evolutions are bout the [Swift package](https://github.com/Orange-OpenSource/ouds-ios/), add in your pull request the details about it (branch to test, associated pull request, etc.). **Copy/paste the Swift pakcage changelog line in the app changelog with cross-linked issues** ; thus for alpha, beta and production builds the changelog of the app will mirror the changelog of the package
+8. If your evolutions are bout the [Swift package](https://github.com/Orange-OpenSource/ouds-ios/), add in your pull request the details about it (branch to test, associated pull request, etc.). **Copy/paste the Swift package changelog line in the app changelog with cross-linked issues** ; thus for alpha, beta and stable builds the changelog of the app will mirror the changelog of the package.
 
 ## Code Guidelines
 
@@ -171,7 +176,7 @@ If your commits embed contributions for other people, do not forget to [add them
 For example, given a commit to fix the issue n°43, the commit should be like:
 
 ```text
-fix: title of your commit (#43)
+fix: title of your commit (Orange-OpenSource/ouds-ios#43)
 
 Some details about the fix you propose
 
@@ -182,7 +187,7 @@ Signed-off-by: Author firstname and lastname <first author email>
 If the commit embeds work of several authors, use the *Co-authored-by* tag (in use in GitHub):
 
 ```text
-fix: title of your commit (#43)
+fix: title of your commit (Orange-OpenSource/ouds-ios#43)
 
 Some details about the fix you propose
 
@@ -197,7 +202,7 @@ If the feature has been reviewed by the product owner, the designers and the acc
 It can help to find who reviewed, in alpha builds, the evolutions. Thus, the message for the merge commit should be like:
 
 ```text
-fix: title of your commit (#43)
+fix: title of your commit (Orange-OpenSource/ouds-ios#43)
 
 Some details about the fix you propose
 
@@ -211,21 +216,20 @@ Signed-off-by: Second author firstname and lastname <second author email>
 Do not forget also to add, in the merge commit, who reviewed the source code evolutions using the [*Reviewed-by*](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst#n525) tag, like:
 
 ```text
-fix: title of your commit (#43)
+fix: title of your commit (Orange-OpenSource/ouds-ios#43)
 
 Some details about the fix you propose
 
 Reviewed-by: Reviewer firstname and lastname <reviewer email>
 Signed-off-by: Author firstname and lastname <first author email>
 ```
 
-For example, for issue n°123 and its pull request n°456, tested by Anton, Iman, Maxime and Benoit, reviewed by Ludovic, authored by Tayeb and Pierre-Yves, and acked by Julien:
+For example, for issue n°123 and its pull request n°456, tested by Anton, Maxime and Benoit, reviewed by Ludovic, authored by Tayeb and Pierre-Yves, and acked by Julien:
 ```text
-refactor: update some things colors and design of the demo app (#123) (#4562)
+refactor: update some things colors and design of the demo app (Orange-OpenSource/ouds-ios#123) (#456)
 
 Some things have been refactored to make incredible things.
 
-Tested-by: Iman Assabah <[email protected]>
 Tested-by: Anton Astafev <[email protected]>
 Tested-by: Benoit Suzanne <[email protected]>
 Tested-by: Maxime Tonnerre <[email protected]>
@@ -240,7 +244,7 @@ Signed-off-by: Pierre-Yves Lapersonne <[email protected]>
 Finaly, if you want to note somewhere you used *generative AI* tool, you can add the field "Assisted-by" in your commit with the model in use and in parenthsies some commercial name.
 
 ```text
-feat: add thousands of tokens (#666)
+feat: add thousands of tokens (Orange-OpenSource/ouds-ios#123)
 
 Add thousands of tokens and hundreds of tests.