diff options
-rw-r--r-- | Configurations/00-base-templates.conf | 2 | ||||
-rw-r--r-- | Configurations/README | 2 | ||||
-rw-r--r-- | Configurations/common0.tmpl | 2 | ||||
-rw-r--r-- | INSTALL | 10 | ||||
-rw-r--r-- | apps/ca.c | 2 | ||||
-rw-r--r-- | crypto/LPdir_unix.c | 2 | ||||
-rw-r--r-- | crypto/evp/e_aes.c | 2 | ||||
-rw-r--r-- | e_os.h | 2 |
8 files changed, 12 insertions, 12 deletions
diff --git a/Configurations/00-base-templates.conf b/Configurations/00-base-templates.conf index 516e3cd525..dd0649d203 100644 --- a/Configurations/00-base-templates.conf +++ b/Configurations/00-base-templates.conf @@ -45,7 +45,7 @@ my %targets=( shared_extension => "", #### Defaults for the benefit of the config targets who don't inherit - #### a BASE and assume Unixly defaults + #### a BASE and assume Unix defaults #### THESE WILL DISAPPEAR IN OpenSSL 1.2 build_scheme => [ "unified", "unix" ], build_file => "Makefile", diff --git a/Configurations/README b/Configurations/README index 4457b94711..d2d893d8d2 100644 --- a/Configurations/README +++ b/Configurations/README @@ -233,7 +233,7 @@ In each table entry, the following keys are significant: apps, as needed by the target. This code cannot be placed in a library, as the rest of the code isn't expected to link to it - explicitely. + explicitly. cpuid_asm_src => assembler implementation of cpuid code as well as OPENSSL_cleanse(). Default to mem_clr.c diff --git a/Configurations/common0.tmpl b/Configurations/common0.tmpl index c0060095ba..03acb3e0b3 100644 --- a/Configurations/common0.tmpl +++ b/Configurations/common0.tmpl @@ -16,7 +16,7 @@ ? () : ( map { @{$unified_info{shared_sources}->{$_}} } keys %{$unified_info{shared_sources}} ), - # Things we explicitely depend on are usually generated + # Things we explicitly depend on are usually generated ( map { $_ eq "" ? () : @{$unified_info{depends}->{$_}} } keys %{$unified_info{depends}} )); our @generated = @@ -614,8 +614,8 @@ Windows, and as a comma separated list of libraries on VMS. RANLIB The library archive indexer. - RC The Windows resources manipulator. - RCFLAGS Flags for the Windows reources manipulator. + RC The Windows resource compiler. + RCFLAGS Flags for the Windows resource compiler. RM The command to remove files and directories. These cannot be mixed with compiling / linking flags given @@ -969,7 +969,7 @@ BUILDFILE Use a different build file name than the platform default - ("Makefile" on Unixly platforms, "makefile" on native Windows, + ("Makefile" on Unix-like platforms, "makefile" on native Windows, "descrip.mms" on OpenVMS). This requires that there is a corresponding build file template. See Configurations/README for further information. @@ -1171,7 +1171,7 @@ part of the file name, i.e. for OpenSSL 1.1.x, 1.1 is somehow part of the name. - On most POSIXly platforms, shared libraries are named libcrypto.so.1.1 + On most POSIX platforms, shared libraries are named libcrypto.so.1.1 and libssl.so.1.1. on Cygwin, shared libraries are named cygcrypto-1.1.dll and cygssl-1.1.dll @@ -1202,7 +1202,7 @@ The seeding method can be configured using the --with-rand-seed option, which can be used to specify a comma separated list of seed methods. However in most cases OpenSSL will choose a suitable default method, - so it is not necessary to explicitely provide this option. Note also + so it is not necessary to explicitly provide this option. Note also that not all methods are available on all platforms. I) On operating systems which provide a suitable randomness source (in @@ -605,7 +605,7 @@ end_of_options: /* * outdir is a directory spec, but access() for VMS demands a * filename. We could use the DEC C routine to convert the - * directory syntax to Unixly, and give that to app_isdir, + * directory syntax to Unix, and give that to app_isdir, * but for now the fopen will catch the error if it's not a * directory */ diff --git a/crypto/LPdir_unix.c b/crypto/LPdir_unix.c index 356089d7fd..b1022895c8 100644 --- a/crypto/LPdir_unix.c +++ b/crypto/LPdir_unix.c @@ -51,7 +51,7 @@ #endif /* - * The POSIXly macro for the maximum number of characters in a file path is + * The POSIX macro for the maximum number of characters in a file path is * NAME_MAX. However, some operating systems use PATH_MAX instead. * Therefore, it seems natural to first check for PATH_MAX and use that, and * if it doesn't exist, use NAME_MAX. diff --git a/crypto/evp/e_aes.c b/crypto/evp/e_aes.c index 0add393276..39eb4f379a 100644 --- a/crypto/evp/e_aes.c +++ b/crypto/evp/e_aes.c @@ -2241,7 +2241,7 @@ static int s390x_aes_ccm_cipher(EVP_CIPHER_CTX *ctx, unsigned char *out, if (!cctx->aes.ccm.len_set) { /*- - * In case message length was not previously set explicitely via + * In case message length was not previously set explicitly via * Update(), set it now. */ ivec = EVP_CIPHER_CTX_iv_noconst(ctx); @@ -245,7 +245,7 @@ extern FILE *_imp___iob; Finally, we add the VMS C facility code 0x35a000, because there are some programs, such as Perl, that will reinterpret the code back to something - POSIXly. 'man perlvms' explains it further. + POSIX. 'man perlvms' explains it further. NOTE: the perlvms manual wants to turn all codes 2 to 255 into success codes (status type = 1). I couldn't disagree more. Fortunately, the |