From a8b2b52fe57249f5093e190eb40def9fed9c9627 Mon Sep 17 00:00:00 2001 From: Daniel Bevenius Date: Wed, 11 Apr 2018 12:57:31 -0400 Subject: [PATCH] Fix minor typos in Configurations/README Reviewed-by: Andy Polyakov Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/5774) --- Configurations/README | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Configurations/README b/Configurations/README index d553cab6d2..4457b94711 100644 --- a/Configurations/README +++ b/Configurations/README @@ -165,7 +165,7 @@ In each table entry, the following keys are significant: that use dlopen() et al but do not have fcntl.h), "DL" (shl_load() et al), "WIN32" and "VMS". - perlasm_scheme => The perlasm method used to created the + perlasm_scheme => The perlasm method used to create the assembler files used when compiling with assembler implementations. shared_target => The shared library building method used. @@ -429,7 +429,7 @@ It's also possible to depend on static libraries explicitly: This should be rarely used, and care should be taken to make sure it's only used when supported. For example, native Windows build doesn't -support build static libraries and DLLs at the same time, so using +support building static libraries and DLLs at the same time, so using static libraries on Windows can only be done when configured 'no-shared'. @@ -445,7 +445,7 @@ library: RENAME[libfoo]=libbar -That lines has "libfoo" get renamed to "libbar". While it makes no +That line has "libfoo" renamed to "libbar". While it makes no sense at all to just have a rename like that (why not just use "libbar" everywhere?), it does make sense when it can be used conditionally. See a little further below for an example. -- 2.25.1