Title Case in markdown

Author: kvakvs

lib/crypto/doc/guides/fips.md

@@ -19,7 +19,7 @@ limitations under the License.
 
 %CopyrightEnd%
 -->
-# FIPS mode
+# FIPS Mode
 
 [](){: #fips } This chapter describes FIPS mode support in the crypto
 application.
@@ -36,7 +36,7 @@ only the validated algorithms provided by the Object Module are accessible,
 other algorithms usually available in OpenSSL (like md5) or implemented in the
 Erlang code (like SRP) are disabled.
 
-## Enabling FIPS mode
+## Enabling FIPS Mode
 
 > #### Warning {: .warning }
 >
@@ -87,7 +87,7 @@ to use copy of OpenSSL, it is time to configure it for FIPS mode.
    `status: active`. The `default` can be disabled in `openssl.cnf` in the
    `[default]` section.
 
-### Building Erlang with FIPS
+### Building Erlang With FIPS
 
 1. Configure and build Erlang/OTP with FIPS support:
    ```bash
@@ -113,7 +113,7 @@ section protected from any concurrently running crypto operations. Furthermore
 in case of failure all crypto calls would have to be disabled from the Erlang or
 nif code. This would be too much effort put into this not too important feature.
 
-## Incompatibilities with regular builds
+## Incompatibilities With Regular Builds
 
 The Erlang API of the crypto application is identical regardless of building
 with or without FIPS support. However the nif code internally uses a different
@@ -124,7 +124,7 @@ functions (`hash_(init|update|final)`, `hmac_(init|update|final)` and
 `stream_(init|encrypt|decrypt)`) is different and incompatible with regular
 builds when compiling crypto with FIPS support.
 
-## Common caveats
+## Common Caveats
 
 In FIPS mode non-validated algorithms are disabled. This may cause some
 unexpected problems in application relying on crypto.
@@ -136,32 +136,30 @@ unexpected problems in application relying on crypto.
 > 140-2 validated cryptographic module if it uses it exclusively for every
 > cryptographic operation.
 
-### Restrictions on key sizes
+### Restrictions On Key Sizes
 
 Although public key algorithms are supported in FIPS mode they can only be used
 with secure key sizes. The Security Policy requires the following minimum
 values:
 
 - **RSA** - 1024 bit
-
 - **DSS** - 1024 bit
-
 - **EC algorithms** - 160 bit
 
-### Restrictions on elliptic curves
+### Restrictions On Elliptic Curves
 
 The Erlang API allows using arbitrary curve parameters, but in FIPS mode only
 those allowed by the Security Policy shall be used.
 
-### Avoid md5 for hashing
+### Avoid MD5 For Hashing
 
 MD5 is a popular choice as a hash function, but it is not secure enough to be
 validated. Try to use sha instead wherever possible.
 
 For exceptional, non-cryptographic use cases one may consider switching to
 `erlang:md5/1` as well.
 
-### Certificates and encrypted keys
+### Certificates And Encrypted Keys
 
 As md5 is not available in FIPS mode it is only possible to use certificates
 that were signed using sha hashing. When validating an entire certificate chain
@@ -171,14 +169,14 @@ For similar dependency on the md5 and des algorithms most encrypted private keys
 in PEM format do not work either. However, the PBES2 encryption scheme allows
 the use of stronger FIPS verified algorithms which is a viable alternative.
 
-### SNMP v3 limitations
+### SNMP v3 Limitations
 
 It is only possible to use `usmHMACSHAAuthProtocol` and `usmAesCfb128Protocol`
 for authentication and privacy respectively in FIPS mode. The snmp application
 however won't restrict selecting disabled protocols in any way, and using them
 would result in run time crashes.
 
-### TLS 1.2 is required
+### TLS 1.2 Is Required
 
 All SSL and TLS versions prior to TLS 1.2 use a combination of md5 and sha1
 hashes in the handshake for various purposes: