Improve list format in Markdownfiles

CONTRIBUTING.md

@@ -78,6 +78,7 @@ introduced behavior, especially for bug fixes and major changes:
     *fails* before your change and *passes* afterward. This makes it easier to
     confirm that the fix addresses the underlying issue and helps prevent
     regressions in the future.
+
   * **New Features or Major Changes:** If you are adding a new feature or making
     major changes to existing functionality, please add tests that cover the
     major parts of that functionality. Aim to have the best code coverage possible.
@@ -88,7 +89,9 @@ We have saved some excellent pull requests we have received in the past in
 case you are looking for some examples:
 
   * [Implement Enum.member? - Pull request](https://github.com/elixir-lang/elixir/pull/992)
+
   * [Add String.valid? - Pull request](https://github.com/elixir-lang/elixir/pull/1058)
+
   * [Implement capture_io for ExUnit - Pull request](https://github.com/elixir-lang/elixir/pull/1059)
 
 ## Reviewing changes
@@ -122,27 +125,31 @@ guidelines on licensing and compliance. Below is a summary of the key points
 affecting **all external contributors**:
 
   * Accepted Licenses: Any code contributed must be licensed under the
-  `Apache-2.0` license.
+    `Apache-2.0` license.
+
   * SPDX License Headers: With the exception of approved test fixture files,
-  all new or modified files in a pull request must include correct SPDX
-  headers. If you are creating a new file under the `Apache-2.0` license, for
-  instance, please use:
+    all new or modified files in a pull request must include correct SPDX
+    headers. If you are creating a new file under the `Apache-2.0` license, for
+    instance, please use:
 
     ```elixir
     # SPDX-License-Identifier: Apache-2.0
     # SPDX-FileCopyrightText: 2021 The Elixir Team
     ```
 
   * No Executable Binaries: Contributions must **not** include any executable
-  binary files. If you require an exception (for example, certain test artifacts),
-  please see the policy on how to request approval and document exceptions.
+    binary files. If you require an exception (for example, certain test artifacts),
+    please see the policy on how to request approval and document exceptions.
+
   * Preserving Copyright and License Info: If you copy code from elsewhere,
-  ensure that **all original copyright and license notices remain intact**. If
-  they are missing or incomplete, you must add them.
+    ensure that **all original copyright and license notices remain intact**. If
+    they are missing or incomplete, you must add them.
+
   * Failure to Comply: Pull requests that do not meet these licensing and
-  compliance standards will be rejected or require modifications before merging.
+    compliance standards will be rejected or require modifications before merging.
+
   * Developer Certificate of Origin: All contributions are subject to the
-  Developer Certificate of Origin.
+    Developer Certificate of Origin.
 
     ```text
     By making a contribution to this project, I certify that:

OPEN_SOURCE_POLICY.md

@@ -30,9 +30,10 @@ All code released by the Elixir team is licensed under the
 licenses are recognized as permissible in this project:
 
   - The Unicode license, as documented at
-  [LicenseRef-scancode-unicode](./LICENSES/LicenseRef-scancode-unicode.txt)
+    [LicenseRef-scancode-unicode](./LICENSES/LicenseRef-scancode-unicode.txt)
+
   - The Elixir Trademark Policy, as documented at
-  [LicenseRef-elixir-trademark-policy](./LICENSES/LicenseRef-elixir-trademark-policy.txt)
+    [LicenseRef-elixir-trademark-policy](./LICENSES/LicenseRef-elixir-trademark-policy.txt)
 
 These licenses are considered acceptable for any files or code that form part of
 an Elixir repository. If a contribution requires a different license, it must