Fix some spelling misstakes

4 files changed, 10 insertions, 10 deletions

diff --git a/HOWTO/INSTALL.md b/HOWTO/INSTALL.md
index 5b3a09df2b..7a7e63164c 100644
--- a/HOWTO/INSTALL.md
+++ b/HOWTO/INSTALL.md
@@ -385,7 +385,7 @@ Some of the available `configure` options are:
 *   `--enable-static-{nifs,drivers}` - To allow usage of nifs and drivers on OSs
     that do not support dynamic linking of libraries it is possible to statically
     link nifs and drivers with the main Erlang VM binary. This is done by passing
-    a comma seperated list to the archives that you want to statically link. e.g.
+    a comma separated list to the archives that you want to statically link. e.g.
     `--enable-static-nifs=/home/$USER/my_nif.a`. The path has to be absolute and the
     name of the archive has to be the same as the module, i.e. `my_nif` in the
     example above. This is also true for drivers, but then it is the driver name
diff --git a/erts/configure.in b/erts/configure.in
index f66110b98b..06e2490e0c 100644
--- a/erts/configure.in
+++ b/erts/configure.in
@@ -446,13 +446,13 @@ else
 fi
 
 AC_ARG_ENABLE(static-nifs,
-AS_HELP_STRING([--enable-static-nifs], [link nifs statically. If yes then all nifs in all Erlang/OTP applications will be statically linked into the main binary. It is also possible to give a list of nifs that should be linked statically. The list should be a comma seperated and contain the absolute path to a .a archive for each nif that is to be statically linked. The name of the .a archive has to be the same as the name of the nif. Note that you have to link any external dependencies that the nifs have to the main binary, so for the crypto nif you want to pass LIBS=-lcrypto to configure.]),
+AS_HELP_STRING([--enable-static-nifs], [link nifs statically. If yes then all nifs in all Erlang/OTP applications will be statically linked into the main binary. It is also possible to give a list of nifs that should be linked statically. The list should be a comma separated and contain the absolute path to a .a archive for each nif that is to be statically linked. The name of the .a archive has to be the same as the name of the nif. Note that you have to link any external dependencies that the nifs have to the main binary, so for the crypto nif you want to pass LIBS=-lcrypto to configure.]),
 	       STATIC_NIFS="$enableval",
 	       STATIC_NIFS=no)
 AC_SUBST(STATIC_NIFS)
 
 AC_ARG_ENABLE(static-drivers,
-AS_HELP_STRING([--enable-static-drivers], [comma seperated list of linked-in drivers to link statically with the main binary. The list should contain the absolute path to a .a archive for each driver that is to be statically linked. The name of the .a archive has to be the same as the name of the driver.]),
+AS_HELP_STRING([--enable-static-drivers], [comma separated list of linked-in drivers to link statically with the main binary. The list should contain the absolute path to a .a archive for each driver that is to be statically linked. The name of the .a archive has to be the same as the name of the driver.]),
 	       STATIC_DRIVERS="$enableval",
 	       STATIC_DRIVERS=no)
 AC_SUBST(STATIC_DRIVERS)
diff --git a/lib/inets/doc/src/httpd.xml b/lib/inets/doc/src/httpd.xml
index 3830b2e5ab..4ca038cc99 100644
--- a/lib/inets/doc/src/httpd.xml
+++ b/lib/inets/doc/src/httpd.xml
@@ -139,7 +139,7 @@
       <marker id="prop_server_root"></marker>
       <tag>{server_root, path()} </tag>
       <item> 
-	<p>Defines the servers home directory where log files etc can
+	<p>Defines the server's home directory where log files etc can
 	be stored. Relative paths specified in other properties refer
 	to this directory. </p>
       </item>
@@ -904,7 +904,7 @@ bytes
         <p>Fetches information about the HTTP server. When called
 	with only the pid all properties are fetched, when called
 	with a list of specific properties they are fetched.
-	Available properties are the same as the servers start options. 
+	Available properties are the same as the server's start options. 
 	</p>
 	
 	<note><p>Pid is the pid returned from inets:start/[2,3]. 
@@ -930,7 +930,7 @@ bytes
         <p>Fetches information about the HTTP server. When called with
 	only the Address and Port all properties are fetched, when
 	called with a list of specific properties they are fetched.
-	Available properties are the same as the servers start
+	Available properties are the same as the server's start
 	options.
 	</p>
 
@@ -956,7 +956,7 @@ bytes
 	  server. Incoming requests will be answered with a temporary
 	  down message during the time the it takes to reload.</p>
 	
-	<note><p>Available properties are the same as the servers
+	<note><p>Available properties are the same as the server's
 	    start options, although the properties bind_address and
 	    port can not be changed.</p></note>
 	
@@ -1068,7 +1068,7 @@ bytes
       <type>
         <v>OldData = list()</v>
         <v>NewData = [{response,{StatusCode,Body}}] | [{response,{response,Head,Body}}] |  [{response,{already_sent,Statuscode,Size}}] </v>
-        <v>StausCode = integer()</v>
+        <v>StatusCode = integer()</v>
         <v>Body = io_list() | nobody | {Fun, Arg}</v>
         <v>Head = [HeaderOption]</v>
         <v>HeaderOption = {Option, Value} | {code, StatusCode}</v>
diff --git a/lib/ose/doc/src/ose_intro.xml b/lib/ose/doc/src/ose_intro.xml
index b5e3ef8b33..0ed470890b 100644
--- a/lib/ose/doc/src/ose_intro.xml
+++ b/lib/ose/doc/src/ose_intro.xml
@@ -65,7 +65,7 @@ erl
 /home/erlang
 --</code>
     <p>
-      The arguments are printed on seperate lines to make it possible to know
+      The arguments are printed on separate lines to make it possible to know
       what has to be quoted with &quot;. Each line is one quotable unit.
       So taking the arguments above you can supply them to pm_create or
       just execute directly on the command line. For example:</p>
@@ -75,7 +75,7 @@ pid: 0x110059
 rtose@acp3400> pm_start 0x110059</code>
     <p>
       Also note that since we are running erl to figure out the arguments on a
-      seperate machine the paths have to be updated. In the example above
+      separate machine the paths have to be updated. In the example above
       <c>/usr/local/lib/erlang</c> was replaced by <c>/mst/erlang/</c>. The
       goal is to in future releases not have to do the special argument handling
       but for now (OTP 17.0) you have to do it.