Merge pull request #15939 from ethereum/release_checklist_remove_double_backticks

Remove double backticks and indented bullet points from Markdown files

Author: cameel

CODING_STYLE.md

@@ -110,9 +110,9 @@ Use `solAssert` and `solUnimplementedAssert` generously to check assumptions tha
 4. Favour declarations close to use; do not habitually declare at top of scope ala C.
 5. Pass non-trivial parameters as const reference, unless the data is to be copied into the function, then either pass by const reference or by value and use std::move.
 6. If a function returns multiple values, use std::tuple (std::pair acceptable) or better introduce a struct type. Do not use */& arguments.
-7. Use parameters of pointer type only if ``nullptr`` is a valid argument, use references otherwise. Often, ``std::optional`` is better suited than a raw pointer.
+7. Use parameters of pointer type only if `nullptr` is a valid argument, use references otherwise. Often, `std::optional` is better suited than a raw pointer.
 8. Never use a macro where adequate non-preprocessor C++ can be written.
-9. Only use ``auto`` if the type is very long and rather irrelevant.
+9. Only use `auto` if the type is very long and rather irrelevant.
 10. Do not pass bools: prefer enumerations instead.
 11. Prefer enum class to straight enum.
 12. Always initialize POD variables, even if their value is overwritten later.