Remove trailing spaces

wiki/src/contribute/merge_policy/submit.mdwn

@@ -50,7 +50,7 @@ To submit your branch for review:
          - Summarize what problem this MR will fix, in terms of impact on users.
          - Reference the issues this MR will solve: `Closes #xxx, #yyyy`.
       - If it's obvious to you who can, and should, review your branch: assign
-        the MR to that person.  
+        the MR to that person.
         Else, leave the MR unassigned:
         the [[Foundations Team|working_together/roles/foundations_team]] will
         either handle the review themselves or help you find a suitable reviewer.

wiki/src/contribute/working_together/GitLab.mdwn

@@ -68,26 +68,26 @@ Apart of that, you may consider these labels as optional.
 Closing an issue means one of:
 
  - The bugfix or feature the issue is about:
- 
+
     - was merged and will be in a future release
     - or is already available to our users
 
    The _Milestone_ value tells in which case we are.
 
  - We've rejected it.
- 
+
    For example: it does not fit into Tails' mission,
    or the problem shall be resolved elsewhere than in Tails.
 
    To reject an issue, create a comment that:
-   
+
     - explains why you're rejecting it
     - adds the _Rejected_ label (`/label Rejected`)
 
  - It duplicates another issue.
- 
+
    To mark an issue as a duplicate, create a comment that:
-   
+
     - mentions the other, duplicated issue
     - adds the _Duplicate_ label (`/label Duplicate`)
 
@@ -103,7 +103,7 @@ To this aim, most tasks should be up for grabs for anyone who has spare capacity
 and the required skills: [Don't Lick the
 Cookie](https://www.benday.com/2016/10/21/scrum-dont-lick-the-cookie/).
 
-So in general, issues and merge requests should not be assigned to anyone. 
+So in general, issues and merge requests should not be assigned to anyone.
 
 This being said, we do assign them if at least one of these conditions is
 met:
@@ -337,7 +337,7 @@ you can:
    on issues and merge requests, modify issues metadata
 
    To do so, reply to an email notification you've received from GitLab.
-   
+
    Write your email just as if you [replied from the
    web].
    In particular:
@@ -348,7 +348,7 @@ you can:
       [[!tails_gitlab help/user/project/quick_actions.html desc="Quick actions"]].
 
  - Create new issues
- 
+
    See [[!tails_gitlab help/user/project/issues/managing_issues.html#new-issue-via-email desc="New issue via email"]]
    in the GitLab documentation.