From 879365e6d4a53d80e83bbe468fcf2cdd02d30ba1 Mon Sep 17 00:00:00 2001 From: Richard Levitte Date: Tue, 12 Jan 2021 15:44:43 +0100 Subject: Make header references conform with man-pages(7) in all manuals MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Details from man-pages(7) that are used: Formatting conventions (general) ... Filenames (whether pathnames, or references to header files) are always in italics (e.g., ), except in the SYNOPSIS section, where in‐ cluded files are in bold (e.g., #include ). When referring to a standard header file include, specify the header file surrounded by angle brackets, in the usual C way (e.g., ). ... Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/13843) --- doc/man3/ASYNC_WAIT_CTX_new.pod | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/man3/ASYNC_WAIT_CTX_new.pod') diff --git a/doc/man3/ASYNC_WAIT_CTX_new.pod b/doc/man3/ASYNC_WAIT_CTX_new.pod index f1d6a02219..d6e5d38a12 100644 --- a/doc/man3/ASYNC_WAIT_CTX_new.pod +++ b/doc/man3/ASYNC_WAIT_CTX_new.pod @@ -192,12 +192,12 @@ ASYNC_WAIT_CTX_get_status() returns the engine status. =head1 NOTES -On Windows platforms the openssl/async.h header is dependent on some -of the types customarily made available by including windows.h. The +On Windows platforms the F<< >> header is dependent on some +of the types customarily made available by including F<< >>. The application developer is likely to require control over when the latter is included, commonly as one of the first included headers. Therefore, it is defined as an application developer's responsibility to include -windows.h prior to async.h. +F<< >> prior to F<< >>. =head1 SEE ALSO -- cgit v1.2.3