Use fips=yes consistently in documentation

The documentation for ``EVP_default_properties_is_fips_enabled()`` uses ``fips=yes`` in one place and ``fips=true`` in another place. Stick to ``fips=yes`` like everywhere else. Signed-off-by: Christian Heimes <[email protected]> Reviewed-by: Matt Caswell <[email protected]> Reviewed-by: Tomas Mraz <[email protected]> (Merged from openssl#11723)
tmshort · May 5, 2020 · 6763f9c · 6763f9c
1 parent 278260b
commit 6763f9c
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/doc/man3/EVP_set_default_properties.pod b/doc/man3/EVP_set_default_properties.pod
@@ -44,7 +44,7 @@ EVP_set_default_properties() and  EVP_default_properties_enable_fips() return 1
 on success, or 0 on failure. An error is placed on the the error stack if a
 failure occurs.
 
-EVP_default_properties_is_fips_enabled() returns 1 if the 'fips=true' default
+EVP_default_properties_is_fips_enabled() returns 1 if the 'fips=yes' default
 property is set for the given I<libctx>, otherwise it returns 0.
 
 =head1 SEE ALSO