Development-workflow.md

@@ -8,7 +8,7 @@
 
 #### As an external
 
-Open an issue and change ``Description`` template to ``User-Request``. Fill the template describing the issue
+Open an issue and change `Description` template to `User-Request`. Fill the template describing the issue
 
 #### As a developer
 
@@ -28,9 +28,8 @@ Open an issue and change ``Description`` template to ``User-Request``. Fill the
 
 1. Create a local branch with a specific prefix to its name :
    * `fix_...` is the branch/the issue is a malfunction to repair.
-   * `chore_...` if the issue is a minor such as updating a dependency.
-   * `refactor_...` if the issue is about a refactoring.
-   * `feat_...` if the issue is about a new feature.
+   * `chore_...` if the issue is a minor such as updating a dependency or reformatting code.
+   * `feat_...` if the issue is about a new feature or a refactor.
 2. Once you have pushed your 1st commit, you can create an associated Merge Request(MR) to your branch. Since the (in MR title add `Draft: <MR title>` or check the draft checkbox when creating/editing)
 3. Mention the issue associated in the merge request description. This will have as consequence that all the MR associated to an issue will be shown on the issue page. This allows to track the evolution of the progress on a given issue.
 4. When the MR is ready remove the part `Draft :` from the title. This allows the reviewers to know when they can review the code.
@@ -86,4 +85,4 @@ You can find the issue board here: https://gitlab.eclipse.org/groups/eclipse/aid
 There are multiple issue boards:
 
 * Development: Show issues sorted by status
-* Discussions: Show issues requiring a discussion
+* Discussions: Show issues requiring a discussion
\ No newline at end of file