Documentation fixes and update

Author: kvakvs

lib/crypto/src/crypto.erl

@@ -106,7 +106,8 @@ The exception `error:notsup` signifies that the algorithm is known but is not
 supported by current underlying libcrypto or explicitly disabled when building
 that.
 
-For a list of supported algorithms, see [supports(ciphers)](`supports/1`).
+For a list of supported algorithms, see [supports(ciphers)](`supports/1`)
+and [supports()](`supports/0`).
 
 [](){: #error_3tup }
 
@@ -151,7 +152,7 @@ end
 """.
 
 
--export([start/0, stop/0, info/0, info_lib/0, info_fips/0, supports/0, enable_fips_mode/1,
+-export([start/0, stop/0, info/0, info_lib/0, info_fips/0, enable_fips_mode/1,
          version/0, bytes_to_integer/1]).
 -export([cipher_info/1, hash_info/1]).
 -export([hash/2, hash_xof/3, hash_init/1, hash_update/2, hash_final/1, hash_final_xof/2]).
@@ -238,7 +239,7 @@ end
 
          hash_equals/2,
 
-         supports/1,
+         supports/0, supports/1,
          mac/3, mac/4, macN/4, macN/5,
          mac_init/2, mac_init/3, mac_update/2, mac_final/1, mac_finalN/2
         ]).
@@ -836,15 +837,32 @@ Get a collection of all supported crypto algorithms, grouped per type.
 
 If FIPS mode is enabled and supported, the return value will also include an additional key:
 `fips_forbidden`, containing lists of algorithms which are not allowed to use under FIPS mode.
-Each algorithm is tried once on the `crypto` application startup.
-The `fips_forbidden` results are also grouped in the same way as the  results. The `rsa_opts` key in
-`fips_forbidden` is returned for completeness and is always an empty list, because validity of
-`rsa_opts` under FIPS can only be determined based on multiple other `rsa_opts` passed together.
+Each algorithm is tried once during the `crypto` application startup.
+
+The `rsa_opts` key in `fips_forbidden` is returned for completeness and is always an empty list,
+because the validity of each `rsa_opts` option under FIPS can only be determined based on
+multiple other `rsa_opts` passed together.
+
+Example response with FIPS enabled:
+```erlang
+[{hashs, [...
+ {ciphers, ...
+ {kems, []},
+ {public_keys, ...
+ {macs, ...
+ {curves, ...
+ {rsa_opts, ...
+ {fips_forbidden,[{hashs,[blake2s,blake2b,sm3,ripemd160,md5,md4]},
+                  {ciphers,[chacha20,sm4_ctr,sm4_ofb,sm4_cfb,sm4_ecb,sm4_cbc,...]},
+                  {kems,[mlkem1024,mlkem768,mlkem512]},
+                  {public_keys,[srp,eddh,eddsa,ecdh,ecdsa,ec_gf2m,dss]},
+                  {macs,[hmac,poly1305]},
+                  {curves,[secp256r1]},
+                  {rsa_opts,[]}]}]
+```
 """.
--spec supports() -> [
-    supported_result_item()
-    | {fips_forbidden, [supported_result_item()]}
-].
+-doc(#{group => <<"Utility Functions">>}).
+-spec supports() -> [supported_result_item() | {fips_forbidden, [supported_result_item()]}].
 supports() ->
     %% Add FIPS-disabled algorithms separately for the users to see
     FIPSForbidden = case application:get_env(crypto, fips_mode, false) of