Fix typos

man/mad.htm

@@ -68,8 +68,8 @@
         <h4>main(list(string())) -> integer().</h4>
         <p>Simple yet understandable command processing and error loop.
            Function <b>atomize/1</b> helps to accumulate
-           known agruments as atoms. Function <b>profile/0</b>
-           retrives module with MAD API implementation.
+           known arguments as atoms. Function <b>profile/0</b>
+           retrieves module with MAD API implementation.
            <b>main/1</b> function returns error status to OS with halt.</p>
         <figure><code>
  main(Params) ->

tex/bundles.tex

@@ -6,7 +6,7 @@ The key feature of mad is ability to create single-file bundled web sites.
 Thus making dream to boot simpler than node.js come true.
 This bundle target is ready to run on Windows, Linux and Mac.
 
-To make this possible we implemented a zip filesytem inside escript.
+To make this possible we implemented a zip filesystem inside escript.
 mad packages priv directories along with ebin and configs.
 You can redefine each file in zip fs inside target
 escript by creation the copy with same path locally near escript.

tex/commands.tex

@@ -28,7 +28,7 @@ In rebar-like managers we are selecting deps from rebar.config:
 \end{lstlisting}
 \vspace{1\baselineskip}
 
-The search sequence for dependecies is follows. First mad will try to
+The search sequence for dependencies is follows. First mad will try to
 reach global package repository at \footahref{http://synrc.com/apps/index.txt}{http://synrc.com/apps/index.txt},
 this address is configurable. No application server is required for mad
 package management, only static files with OTP application format.
@@ -76,7 +76,7 @@ Performs compilation of all known compilations backends in complilation profile
 \vspace{1\baselineskip}
 
 \subsection{release, rel, bundle, bun}
-Taking all dependecies and resolve boot sequence according to dependecy order.
+Taking all dependencies and resolve boot sequence according to dependency order.
 Storing this value in .applist. If release type is not defined ({\bf beam} in following example),
 then {\bf script} release will be taken as a default.
 \vspace{1\baselineskip}

tex/config.tex

@@ -5,13 +5,13 @@
 mad uses {\bf rebar.config} filename to load mad configuration.
 Despite mad is no fully rebar compatible (e.g. it can't uses
 rebar plugins, ports compilation is rather different, etc),
-it uses its name to achive certail level of compatibility.
+it uses its name to achieve certail level of compatibility.
 
 \subsection{deps}
 
 deps is the core option of mad. It says which OTP applications
-shold be used and where they could be found. Yoy may also specify
-versions. Here is simpliest example:
+should be used and where they could be found. Yoy may also specify
+versions. Here is simplest example:
 
 \vspace{1\baselineskip}
 \begin{lstlisting}[caption=deps Option]

tex/deps.tex

@@ -29,10 +29,10 @@ Specifically two kinds of directory layouts:
 
 As you may know you can create OTP releases systools from sasl application.
 mad currently creates releases with systools, but manually manages binary access:
-from local erlang or public applcation depot.
+from local erlang or public application depot.
 
 To bundle binary BEAM or LING along with synrc spplications MAD can use
-global repository statically avaliable at Github Pages:
+global repository statically available at Github Pages:
 
 \vspace{1\baselineskip}
 \begin{lstlisting}

tex/index.tex

@@ -16,7 +16,7 @@ You can make containers from different type of packages, like making runc contai
 
 \subsection{OTP Compliant}
 Mad supports ERTS boot files generation with systools and erlang application format used by OTP.
-This is the main format of application repository. Also boot files are suported on both LING and BEAM.
+This is the main format of application repository. Also boot files are supported on both LING and BEAM.
 
 \subsection{Tiny Size}
 And the good part: