docs: replace dots with dashes in markdown enums

We use dashes instead of dots nearly everywhere except for those few
cases. This commit addresses this issues and brings more coherency into
it.

Closes #7093

diff --git a/docs/CONTRIBUTE.md b/docs/CONTRIBUTE.md
index 8b97009825a6a0adff89a3dff2a66f0299acacd8..115a2c22c7a74496ed7c2535d27db3b3597def62 100644 (file)
--- a/docs/CONTRIBUTE.md
+++ b/docs/CONTRIBUTE.md
@@ -304,4 +304,4 @@ For Windows:
  - [https://gnuwin32.sourceforge.io/packages/diffutils.htm](https://gnuwin32.sourceforge.io/packages/diffutils.htm)
 
 ### Useful resources
-* [Webinar on getting code into cURL](https://www.youtube.com/watch?v=QmZ3W1d6LQI)
+ - [Webinar on getting code into cURL](https://www.youtube.com/watch?v=QmZ3W1d6LQI)

diff --git a/docs/INSTALL.md b/docs/INSTALL.md
index 8e121bca9ef28cee1e5ef19799c4c74a29cd301d..81a1e3959bc7c2b85e9d19964ac198e64a5c1f86 100644 (file)
--- a/docs/INSTALL.md
+++ b/docs/INSTALL.md
@@ -373,14 +373,14 @@ before Android M.
 
 For IBM i (formerly OS/400), you can use curl in two different ways:
 
-* Natively, running in the **ILE**. The obvious use is being able to call curl
+- Natively, running in the **ILE**. The obvious use is being able to call curl
   from ILE C or RPG applications.
-  * You will need to build this from source. See `packages/OS400/README` for
+  - You will need to build this from source. See `packages/OS400/README` for
     the ILE specific build instructions.
-* In the **PASE** environment, which runs AIX programs. curl will be built as
+- In the **PASE** environment, which runs AIX programs. curl will be built as
   it would be on AIX.
-  * IBM provides builds of curl in their Yum repository for PASE software.
-  * To build from source, follow the Unix instructions.
+  - IBM provides builds of curl in their Yum repository for PASE software.
+  - To build from source, follow the Unix instructions.
 
 There are some additional limitations and quirks with curl on this platform;
 they affect both environments.
@@ -398,9 +398,9 @@ getaddrinfo() thread failed to start
 
 Don't panic! curl and your program aren't broken. You can fix this by:
 
-* Set the environment variable `QIBM_MULTI_THREADED` to `Y` before starting
+- Set the environment variable `QIBM_MULTI_THREADED` to `Y` before starting
   your program. This can be done at whatever scope you feel is appropriate.
-* Alternatively, start the job with the `ALWMLTTHD` parameter set to `*YES`.
+- Alternatively, start the job with the `ALWMLTTHD` parameter set to `*YES`.
 
 # Cross compile