Remove unnecessary bold tags in CT pods

[openssl.git] / doc / crypto / SCT_new.pod

diff --git a/doc/crypto/SCT_new.pod b/doc/crypto/SCT_new.pod
index a9534d2da976ba9a384b76e9a8d923e5d2efdb6b..27bf2361d2cf39dc50eb3aaf0a9f59e591d2a4e6 100644 (file)
--- a/doc/crypto/SCT_new.pod
+++ b/doc/crypto/SCT_new.pod
@@ -54,41 +54,41 @@ record a certificate. By cryptographically verifying that a log did indeed issue
 an SCT, some confidence can be gained that the certificate is publicly known.
 
 An internal representation of an SCT can be created in one of two ways.
-The first option is to create a blank SCT, using B<SCT_new>(), and then populate
+The first option is to create a blank SCT, using SCT_new(), and then populate
 it using:
 
 =over
 
-=item * B<SCT_set_version>() to set the SCT version.
+=item * SCT_set_version() to set the SCT version.
 
 Only SCT_VERSION_V1 is currently supported.
 
-=item * B<SCT_set_log_entry_type>() to set the type of certificate the SCT was issued for:
+=item * SCT_set_log_entry_type() to set the type of certificate the SCT was issued for:
 
 B<CT_LOG_ENTRY_TYPE_X509> for a normal certificate.
 B<CT_LOG_ENTRY_TYPE_PRECERT> for a pre-certificate.
 
-=item * B<SCT_set0_log_id>() or B<SCT_set1_log_id>() to set the LogID of the CT log that the SCT came from.
+=item * SCT_set0_log_id() or SCT_set1_log_id() to set the LogID of the CT log that the SCT came from.
 
 The former takes ownership, whereas the latter makes a copy.
 See RFC 6962, Section 3.2 for the definition of LogID.
 
-=item * B<SCT_set_timestamp>() to set the time the SCT was issued (epoch time in milliseconds).
+=item * SCT_set_timestamp() to set the time the SCT was issued (epoch time in milliseconds).
 
-=item * B<SCT_set_signature_nid>() to set the NID of the signature.
+=item * SCT_set_signature_nid() to set the NID of the signature.
 
-=item * B<SCT_set0_signature>() or B<SCT_set1_signature>() to set the signature itself.
+=item * SCT_set0_signature() or SCT_set1_signature() to set the raw signature value.
 
 The former takes ownership, whereas the latter makes a copy.
 
-=item * B<SCT_set0_extensions>() or B<SCT_set1_extensions> to provide SCT extensions.
+=item * SCT_set0_extensions() or B<SCT_set1_extensions> to provide SCT extensions.
 
 The former takes ownership, whereas the latter makes a copy.
 
 =back
 
 Alternatively, the SCT can be pre-populated from the following data using
-B<SCT_new_from_base64>():
+SCT_new_from_base64():
 
 =over
 
@@ -109,7 +109,7 @@ B<CT_LOG_ENTRY_TYPE_PRECERT> for a pre-certificate.
 
 =back
 
-B<SCT_set_source>() can be used to record where the SCT was found
+SCT_set_source() can be used to record where the SCT was found
 (TLS extension, X.509 certificate extension or OCSP response). This is not
 required for verifying the SCT.
 
@@ -121,20 +121,20 @@ success, 0 on failure. They will not make changes on failure.
 Most of the setters will reset the validation status of the SCT to
 SCT_VALIDATION_STATUS_NOT_SET (see L<SCT_verify(3)>).
 
-B<SCT_set_source>() will call B<SCT_set_log_entry_type>() if the type of
+SCT_set_source() will call SCT_set_log_entry_type() if the type of
 certificate the SCT was issued for can be inferred from where the SCT was found.
 For example, an SCT found in an X.509 extension must have been issued for a pre-
 certificate.
 
-B<SCT_set_source>() will not refuse unknown values.
+SCT_set_source() will not refuse unknown values.
 
 =head1 RETURN VALUES
 
-B<SCT_set_version>() returns 1 if the specified version is supported, 0 otherwise.
+SCT_set_version() returns 1 if the specified version is supported, 0 otherwise.
 
-B<SCT_set_log_entry_type>() returns 1 if the specified log entry type is supported, 0 otherwise.
+SCT_set_log_entry_type() returns 1 if the specified log entry type is supported, 0 otherwise.
 
-B<SCT_set0_log_id>() and B<SCT_set1_log_id> return 1 if the specified LogID is a
+SCT_set0_log_id() and B<SCT_set1_log_id> return 1 if the specified LogID is a
 valid SHA-256 hash, 0 otherwise. Aditionally, B<SCT_set1_log_id> returns 0 if
 malloc fails.