tidy-up: Markdown, clang-format nits

- drop leading indent from Markdown.
- switch to Markdown section markers where missing.
- move `&&` and `||` to the end of the line (C, Perl).
- openssl: add parenthesis to an if sub-expression.
- misc clang-format nits.
- unfold Markdown links.
- SSL-PROBLEMS.md: drop stray half code-fence.

Closes #20402

docs/RELEASE-PROCEDURE.md

@@ -4,11 +4,9 @@ Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
 SPDX-License-Identifier: curl
 -->
 
-curl release procedure - how to do a release
-============================================
+# curl release procedure - how to do a release
 
-in the source code repo
------------------------
+## in the source code repo
 
 - edit `RELEASE-NOTES` to be accurate
 
@@ -30,8 +28,7 @@ in the source code repo
 
 - upload the 8 resulting files to the primary download directory
 
-in the curl-www repo
---------------------
+## in the curl-www repo
 
 - edit `Makefile` (version number and date),
 
@@ -45,13 +42,11 @@ in the curl-www repo
 
   (the website then updates its contents automatically)
 
-on GitHub
----------
+## on GitHub
 
 - edit the newly made release tag so that it is listed as the latest release
 
-inform
-------
+## inform
 
 - send an email to curl-users, curl-announce and curl-library. Insert the
   RELEASE-NOTES into the mail.
@@ -60,16 +55,13 @@ inform
   file to the above lists as well as to `oss-security@lists.openwall.com`
   (unless the problem is unique to the non-open operating systems)
 
-celebrate
----------
+## celebrate
 
 - suitable beverage intake is encouraged for the festivities
 
-curl release scheduling
-=======================
+# curl release scheduling
 
-Release Cycle
--------------
+## Release Cycle
 
 We normally do releases every 8 weeks on Wednesdays. If important problems
 arise, we can insert releases outside the schedule or we can move the release
@@ -94,8 +86,7 @@ of common public holidays or when the lead release manager is unavailable, the
 release date can be moved forwards or backwards a full week. This is then
 advertised well in advance.
 
-Release Candidates
-------------------
+# Release Candidates
 
 We ship release candidate tarballs on three occasions in preparation for the
 pending release:
@@ -119,8 +110,7 @@ limited period of time.
 **Do not use release candidates in production**. They are work in progress.
 Use them for testing and verification only. Use actual releases in production.
 
-Critical problems
------------------
+# Critical problems
 
 We can break the release cycle and do a patch release at any point if a
 critical enough problem is reported. There is no exact definition of how to
@@ -131,8 +121,7 @@ qualify.
 If you think an issue qualifies, bring it to the curl-library mailing list and
 push for it.
 
-Coming dates
-------------
+# Coming dates
 
 Based on the description above, here are some planned future release dates: