diff options
author | Gustaf Neumann <neumann@wu-wien.ac.at> | 2020-07-04 21:58:30 +0200 |
---|---|---|
committer | Dr. Matthias St. Pierre <matthias.st.pierre@ncp-e.com> | 2020-07-24 21:06:32 +0200 |
commit | 6328d3673fabc336e3064368d855c2d1153ef54c (patch) | |
tree | 1af1ce13e4be6582ac1a9039881953c378058b61 /doc/man3 | |
parent | 7a989af7386e97add7c759fda688c5d2e79e812e (diff) |
Fix typos and repeated words
Reviewed-by: Paul Dale <paul.dale@oracle.com>
Reviewed-by: Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com>
(Merged from https://github.com/openssl/openssl/pull/12370)
Diffstat (limited to 'doc/man3')
119 files changed, 224 insertions, 224 deletions
diff --git a/doc/man3/ASN1_INTEGER_get_int64.pod b/doc/man3/ASN1_INTEGER_get_int64.pod index ac6a5799df..b4f961eab8 100644 --- a/doc/man3/ASN1_INTEGER_get_int64.pod +++ b/doc/man3/ASN1_INTEGER_get_int64.pod @@ -81,7 +81,7 @@ instead. In general an B<ASN1_INTEGER> or B<ASN1_ENUMERATED> type can contain an integer of almost arbitrary size and so cannot always be represented by a C -B<int64_t> type. However in many cases (for example version numbers) they +B<int64_t> type. However, in many cases (for example version numbers) they represent small integers which can be more easily manipulated if converted to an appropriate C integer type. diff --git a/doc/man3/ASN1_STRING_length.pod b/doc/man3/ASN1_STRING_length.pod index 85d356540b..595e63ad51 100644 --- a/doc/man3/ASN1_STRING_length.pod +++ b/doc/man3/ASN1_STRING_length.pod @@ -72,7 +72,7 @@ In general it cannot be assumed that the data returned by ASN1_STRING_data() is null terminated or does not contain embedded nulls. The actual format of the data will depend on the actual string type itself: for example for an IA5String the data will be ASCII, for a BMPString two bytes per -character in big endian format, and for an UTF8String it will be in UTF8 format. +character in big endian format, and for a UTF8String it will be in UTF8 format. Similar care should be take to ensure the data is in the correct format when calling ASN1_STRING_set(). diff --git a/doc/man3/ASN1_TIME_set.pod b/doc/man3/ASN1_TIME_set.pod index 5ed817517d..a115db4c85 100644 --- a/doc/man3/ASN1_TIME_set.pod +++ b/doc/man3/ASN1_TIME_set.pod @@ -117,7 +117,7 @@ one or both (depending on the time difference) of B<*pday> and B<*psec> will be positive. If B<to> represents a time earlier than B<from> then one or both of B<*pday> and B<*psec> will be negative. If B<to> and B<from> represent the same time then B<*pday> and B<*psec> will both be zero. -If both B<*pday> and B<*psec> are non-zero they will always have the same +If both B<*pday> and B<*psec> are nonzero they will always have the same sign. The value of B<*psec> will always be less than the number of seconds in a day. If B<from> or B<to> is NULL the current time is used. @@ -167,7 +167,7 @@ format. =head1 BUGS ASN1_TIME_print(), ASN1_UTCTIME_print() and ASN1_GENERALIZEDTIME_print() -do not print out the time zone: it either prints out "GMT" or nothing. But all +do not print out the timezone: it either prints out "GMT" or nothing. But all certificates complying with RFC5280 et al use GMT anyway. Use the ASN1_TIME_normalize() function to normalize the time value before diff --git a/doc/man3/ASN1_TYPE_get.pod b/doc/man3/ASN1_TYPE_get.pod index fb797220a4..f14850b39f 100644 --- a/doc/man3/ASN1_TYPE_get.pod +++ b/doc/man3/ASN1_TYPE_get.pod @@ -33,7 +33,7 @@ up after the call. ASN1_TYPE_set1() sets the value of B<a> to B<type> a copy of B<value>. ASN1_TYPE_cmp() compares ASN.1 types B<a> and B<b> and returns 0 if -they are identical and non-zero otherwise. +they are identical and nonzero otherwise. ASN1_TYPE_unpack_sequence() attempts to parse the SEQUENCE present in B<t> using the ASN.1 structure B<it>. If successful it returns a pointer @@ -62,12 +62,12 @@ length octets). ASN1_TYPE_cmp() may not return zero if two types are equivalent but have different encodings. For example the single content octet of the boolean TRUE -value under BER can have any non-zero encoding but ASN1_TYPE_cmp() will +value under BER can have any nonzero encoding but ASN1_TYPE_cmp() will only return zero if the values are the same. If either or both of the parameters passed to ASN1_TYPE_cmp() is NULL the -return value is non-zero. Technically if both parameters are NULL the two -types could be absent OPTIONAL fields and so should match, however passing +return value is nonzero. Technically if both parameters are NULL the two +types could be absent OPTIONAL fields and so should match, however, passing NULL values could also indicate a programming error (for example an unparsable type which returns NULL) for types which do B<not> match. So applications should handle the case of two absent values separately. @@ -80,7 +80,7 @@ ASN1_TYPE_set() does not return a value. ASN1_TYPE_set1() returns 1 for success and 0 for failure. -ASN1_TYPE_cmp() returns 0 if the types are identical and non-zero otherwise. +ASN1_TYPE_cmp() returns 0 if the types are identical and nonzero otherwise. ASN1_TYPE_unpack_sequence() returns a pointer to an ASN.1 structure or NULL on failure. diff --git a/doc/man3/ASYNC_WAIT_CTX_new.pod b/doc/man3/ASYNC_WAIT_CTX_new.pod index e4d809c08f..6f6a217e16 100644 --- a/doc/man3/ASYNC_WAIT_CTX_new.pod +++ b/doc/man3/ASYNC_WAIT_CTX_new.pod @@ -50,7 +50,7 @@ job in B<*fd>. The number of file descriptors returned will be stored in B<*numfds>. It is the caller's responsibility to ensure that sufficient memory has been allocated in B<*fd> to receive all the file descriptors. Calling ASYNC_WAIT_CTX_get_all_fds() with a NULL B<fd> value will return no file |