small fixes

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>

contributing/reuse.rst

@@ -22,7 +22,7 @@ as follows:
   *   any new file MUST have a SPDX header (copyright and license);
   *   for files that don't support headers (for example binaries, patches etc.) an associated ``.license`` file MUST be included with the relevant SPDX information;
   *   do not add Copyright Year as part of the SPDX header information;
-  *   the general rule for patch files is to use MIT license and *not* the license of the component for which the patch applies - the latter solution would be error-prone and hard to manage and maintain in the long run, and there may be difficult-to-handle cases (what if the patches modifies multiple files in the same component - eg. gcc - which are subject to different licenses?);
+  *   the general rule for patch files is to use the MIT license and *not* the license of the component for which the patch applies - the latter solution would be error-prone and hard to manage and maintain in the long run, and there may be difficult-to-handle cases (what if the patches modifies multiple files in the same component - eg. gcc - which are subject to different licenses);
   *   when modifying a file through this contribution process, you may (but don't have to) claim copyright by adding a copyright line;
   *   you MUST NOT alter copyright statements made by others, but only add your own;
 
@@ -34,8 +34,8 @@ as follows:
     * the exact upstream provenance (repo, revision, path) MUST be identified;
     * you MUST NOT add SPDX headers to Third Party Files;
     * copyright and license information, as well as upstream provenance information (in the "Comment" section), MUST be stored in `.reuse/dep5` following `Debian dep5 specification <https://dep-team.pages.debian.net/deps/dep5/>`_ (see examples below);
-    * you MUST NOT use wildcards (\*) in dep5 "Files" paragraphs even if Debian specs allow it: it may lead to unnoticed errors or inconsistencies in case of future file additions that may be covered by wildcard expressions even if they have a different license
-    * in case of doubts or problems in finding the correct license and copyright information for Third Party Files, contributors may ask project's Legal Team in the project mailing list oniro-dev@eclipse.org.
+    * you MUST NOT use wildcards (\*) in dep5 "Files" paragraphs even if Debian specs allow it: it may lead to unnoticed errors or inconsistencies in case of future file additions that may be covered by wildcard expressions even if they have a different license;
+    * in case of doubts or problems in finding the correct license and copyright information for Third Party Files, contributors may ask the project's Legal Team in the project mailing list oniro-dev@eclipse.org;
 
 
 SPDX Header Example