summaryrefslogtreecommitdiff
path: root/Configurations
diff options
context:
space:
mode:
authorFdaSilvaYY <fdasilvayy@gmail.com>2016-02-26 20:30:15 +0100
committerRich Salz <rsalz@akamai.com>2016-02-27 10:58:16 -0500
commitb6453a68bbb34c901a2eaf24012d0a3afcbf52ff (patch)
treeb69f05bccb9fa9281aba0523d05360b49411e86c /Configurations
parent79302211cc171d5b7c443448434b8565efa1d2c8 (diff)
downloadopenssl-new-b6453a68bbb34c901a2eaf24012d0a3afcbf52ff.tar.gz
GH753: More spelling fix
Signed-off-by: Rich Salz <rsalz@akamai.com> Reviewed-by: Kurt Roeckx <kurt@openssl.org>
Diffstat (limited to 'Configurations')
-rw-r--r--Configurations/10-main.conf4
-rw-r--r--Configurations/README6
-rw-r--r--Configurations/README.design12
3 files changed, 11 insertions, 11 deletions
diff --git a/Configurations/10-main.conf b/Configurations/10-main.conf
index 6e5e71a785..2ad53e7d1b 100644
--- a/Configurations/10-main.conf
+++ b/Configurations/10-main.conf
@@ -284,7 +284,7 @@
# more sense?
# - Keep in mind that the HP compiler by default generates code
# suitable for execution on the host you're currently compiling at.
-# If the toolkit is ment to be used on various PA-RISC processors
+# If the toolkit is meant to be used on various PA-RISC processors
# consider './Configure hpux-parisc-[g]cc +DAportable'.
# - -DMD32_XARRAY triggers workaround for compiler bug we ran into in
# 32-bit message digests. (For the moment of this writing) HP C
@@ -292,7 +292,7 @@
# chew forever:-). For more details look-up MD32_XARRAY comment in
# crypto/sha/sha_lcl.h.
# - originally there were 32-bit hpux-parisc2-* targets. They were
-# scrapped, because a) they were not interchangable with other 32-bit
+# scrapped, because a) they were not interchangeable with other 32-bit
# targets; a) when critical 32-bit assembly modules detect if they
# are executed on PA-RISC 2.0 and thus adequate performance is
# provided.
diff --git a/Configurations/README b/Configurations/README
index c031884896..1885157123 100644
--- a/Configurations/README
+++ b/Configurations/README
@@ -216,7 +216,7 @@ In each table entry, the following keys are significant:
'inherit_from' that indicate what other configurations to inherit
data from. These are resolved recursively.
- Inheritance works as a set of default values that can be overriden
+ Inheritance works as a set of default values that can be overridden
by corresponding key values in the inheriting configuration.
Note 1: any configuration table can be used as a template.
@@ -530,7 +530,7 @@ They are all expected to return a string with the lines they produce.
'lib' has the intended library file name *without*
extension, libobj2shlib is expected to add that.
- 'shlib' has the correcponding shared library name
+ 'shlib' has the corresponding shared library name
*without* extension. 'deps' has the list of other
libraries (also *without* extension) this library
needs to be linked with. 'objs' has the list of
@@ -596,7 +596,7 @@ the build file actions run with the build tree top as current working
directory.
Make sure to end the section with these functions with a string that
-you thing is apropriate for the resulting build file. If nothing
+you thing is appropriate for the resulting build file. If nothing
else, end it like this:
""; # Make sure no lingering values end up in the Makefile
diff --git a/Configurations/README.design b/Configurations/README.design
index 362b967f17..8b94e220e3 100644
--- a/Configurations/README.design
+++ b/Configurations/README.design
@@ -28,11 +28,11 @@ information needed to build output files, and therefore only (with a
few possible exceptions [1]) have information about end products (such
as scripts, library files and programs) and source files (such as C
files, C header files, assembler files, etc). Intermediate files such
-as object files are rarely directly refered to in build.info files (and
+as object files are rarely directly referred to in build.info files (and
when they are, it's always with the file name extension .o), they are
-infered by Configure. By the same rule of minimalism, end product
+inferred by Configure. By the same rule of minimalism, end product
file name extensions (such as .so, .a, .exe, etc) are never mentioned
-in build.info. Their file name extensions will be infered by the
+in build.info. Their file name extensions will be inferred by the
build-file templates, adapted for the platform they are meant for (see
sections on %unified_info and build-file templates further down).
@@ -112,7 +112,7 @@ Unix-like operating systems.
Two things are worth an extra note:
-'DEPEND[cversion.o]' mentiones an object file. DEPEND indexes is the
+'DEPEND[cversion.o]' mentions an object file. DEPEND indexes is the
only location where it's valid to mention them
Lines in 'BEGINRAW'..'ENDRAW' sections must always mention files as
@@ -361,7 +361,7 @@ section above would be digested into a %unified_info table:
},
);
-As can be seen, everything in %unified_info is fairly simple nuggest
+As can be seen, everything in %unified_info is fairly simple suggest
of information. Still, it tells us that to build all programs, we
must build 'apps/openssl', and to build the latter, we will need to
build all its sources ('apps/openssl.o' in this case) and all the
@@ -434,7 +434,7 @@ etc.
'lib' has the intended library file name *without*
extension, libobj2shlib is expected to add that.
- 'shlib' has the correcponding shared library name
+ 'shlib' has the corresponding shared library name
*without* extension. 'deps' has the list of other
libraries (also *without* extension) this library
needs to be linked with. 'objs' has the list of