Fix typos in source code

Signed-off-by: Etienne Millon <etienne@cryptosense.com>

CHANGES.md

@@ -525,7 +525,7 @@ next
 -----------------------
 
 - Fix the error message when there are more than one `<package>.opam`
-  file for a given pacakge
+  file for a given package
 
 - Report an error when in a wrapped library, a module that is not the
   toplevel module depends on the toplevel module. This doesn't make as

CONTRIBUTING.md

@@ -1,5 +1,5 @@
 Dune is an community orientated open source project. It was originally
-developped at [Jane Street][js] and is now maintained by Jane Street,
+developed at [Jane Street][js] and is now maintained by Jane Street,
 [OCamlLabs][ocl] as well as several developers from the OCaml
 community.
 

README.md

@@ -151,6 +151,6 @@ Status
 Dune is now fairly stable and is used by the majority of packages on
 opam. The package is still in beta version as we are waiting for the
 renaming from Jbuilder to dune before releasing version 1.0.0. Note
-that dune will have backward compatiblity with Jbuilder, in particular
+that dune will have backward compatibility with Jbuilder, in particular
 existing Jbuilder projects will continue to be buildable with
 dune.

bin/main.ml

@@ -969,7 +969,7 @@ let rules =
            \   (context <context-name>)\n\
            \   (action  <action>))"
     ; `P {|$(b,<context-name>) is the context is which the action is executed.
-           It is omitted if the action is independant from the context.|}
+           It is omitted if the action is independent from the context.|}
     ; `P {|$(b,<action>) is the action following the same syntax as user actions,
            as described in the manual.|}
     ; `Blocks help_secs

doc/dune-files.rst

@@ -329,7 +329,7 @@ For instance the following ``modes`` fields are all equivalent:
                   (best object)
                   (best shared_object)))
 
-The extensions for the various linking modes are choosen as follow:
+The extensions for the various linking modes are chosen as follows:
 
 ================ ============= =================
 compilation mode binary kind   extensions

doc/project-layout-specification.rst

@@ -26,7 +26,7 @@ Metadata format
 ===============
 
 All configuration files read by Dune are using a syntax similar to the
-one of S-expressions, which is very simple. The Dune langauge can
+one of S-expressions, which is very simple. The Dune language can
 represent three kinds of values: atoms, strings and lists. By
 combining these, it is possible to construct arbitrarily complex
 project descriptions.
@@ -74,12 +74,12 @@ character. Dune recognizes and interprets the following escape
 sequences:
 
 - ``\n`` to represent a newline character
-- ``\r`` to represent a cariage return (character with ASCII code 13)
+- ``\r`` to represent a carriage return (character with ASCII code 13)
 - ``\b`` to represent ASCII character 8
 - ``\t`` to represent a horizontal tab
 - ``\NNN``, a backslash followed by three decimal characters to
   represent the character with ASCII code ``NNN``
-- ``\xHH``, a backslach followed by two hexidecimal characters to
+- ``\xHH``, a backslash followed by two hexadecimal characters to
   represent the character with ASCII code ``HH`` in hexadecimal
 - ``\\``, a double backslash to represent a single backslash
 - ``\%{`` to represent ``%{`` (see :ref:`variables`)

doc/terminology.rst

@@ -71,5 +71,5 @@ Terminology
   profiles are standard:
 
   -  ``release`` which is the profile used for opam releases
-  -  ``dev`` which is the default profile when none is set explicitely, it
+  -  ``dev`` which is the default profile when none is set explicitly, it
      has stricter warnings that the ``release`` one

doc/usage.rst

@@ -160,8 +160,8 @@ Finding external libraries
 When a library is not available in the workspace, dune will look it
 up in the installed world, and expect it to be already compiled.
 
-It looks up external libraries using a specific list of search pathes. A
-list of search pathes is specific to a given build context and is
+It looks up external libraries using a specific list of search paths. A
+list of search paths is specific to a given build context and is
 determined as follow:
 
 #. if the ``ocamlfind`` is present in the ``PATH`` of the context, use each line

dune.descr

@@ -7,7 +7,7 @@ following a very simple s-expression syntax.
 jbuilder is fast, it has very low-overhead and support parallel builds
 on all platforms. It has no system dependencies, all you need to build
 jbuilder and packages using jbuilder is OCaml. You don't need or make
-or bash as long as the packages themselves don't use bash explicitely.
+or bash as long as the packages themselves don't use bash explicitly.
 
 jbuilder supports multi-package development by simply dropping multiple
 repositories into the same directory.

src/build_system.mli

@@ -29,7 +29,7 @@ type extra_sub_directories_to_keep =
 
     Each callback is used to generate the rules for a given directory
     in the corresponding build context. It receive the directory for
-    which to generate the rules and the splitted part of the path after
+    which to generate the rules and the split part of the path after
     the build context. It must return an additional list of
     sub-directories to keep. This is in addition to the ones that are
     present in the source tree and the ones that already contain rules.

src/gen_rules.ml

@@ -368,7 +368,7 @@ module Gen(P : Install_rules.Params) = struct
               Module.Name.Map.mem modules main_module_name) then
             None
           else if Module.Name.Map.mem modules main_module_name then
-            (* This module needs an implementaion for non-jbuilder
+            (* This module needs an implementation for non-jbuilder
                users of the library:
 
                https://github.com/ocaml/dune/issues/567 *)

src/jbuild.mli

@@ -145,8 +145,8 @@ module Public_lib : sig
 end
 
 module Sub_system_info : sig
-  (** The type of all sub-systems informations. This type is what we
-      get just after parsing a [jbuild] file. *)
+  (** The type of all kind of sub-system information.
+      This type is what we get just after parsing a [jbuild] file. *)
   type t = ..
   type sub_system = t = ..
 

src/lib.mli

@@ -275,7 +275,7 @@ module DB : sig
 
   val available : t -> string -> bool
 
-  (** Retreive the compile informations for the given library. Works
+  (** Retrieve the compile information for the given library. Works
       for libraries that are optional and not available as well. *)
   val get_compile_info : t -> ?allow_overlaps:bool -> string -> Compile.t
 

src/menhir.ml

@@ -13,7 +13,7 @@ type stanza =
 
 module type PARAMS = sig
 
-  (* [sctx] is the super context. It stores all the informations about the
+  (* [sctx] is the super context. It stores all the information about the
      current build context. The current compiler can be obtained via
      [(SC.context sctx).ocamlc]. *)
 

src/ocaml-config/ocaml_config.mli

@@ -34,7 +34,7 @@ val make : Vars.t -> (t, string) Result.t
 (** {1 Query} *)
 
 (** The following parameters match the variables in the output of
-    [ocamlc -config] but are stable accross versions of OCaml. *)
+    [ocamlc -config] but are stable across versions of OCaml. *)
 
 val version                  : t -> int * int * int
 val version_string           : t -> string

src/scheduler.mli

@@ -20,11 +20,11 @@ val set_status_line_generator : (unit -> string option) -> unit Fiber.t
 
 val set_concurrency : int -> unit Fiber.t
 
-(** Scheduler informations *)
+(** Scheduler information *)
 type t
 
 (** Wait until less tham [!Clflags.concurrency] external processes are running and return
-    the scheduler informations. *)
+    the scheduler information. *)
 val wait_for_available_job : unit -> t Fiber.t
 
 (** Logger *)

src/stdune/sexp.mli

@@ -85,7 +85,7 @@ module Of_sexp : sig
       S-expressions.
 
       It is possible to switch between the two mode at any time using
-      the approriate combinator. Some primitives can be used in both
+      the appropriate combinator. Some primitives can be used in both
       mode while some are specific to one mode.  *)
   type ('a, 'kind) parser
 
@@ -97,7 +97,7 @@ module Of_sexp : sig
 
   (** [parse parser context sexp] parse a S-expression using the
       following parser. The input consist of a single
-      S-expression. [context] allows to pass extra informations such as
+      S-expression. [context] allows to pass extra information such as
       versions to individual parsers. *)
   val parse : 'a t -> Univ_map.t -> ast -> 'a
 

src/sub_system.ml

@@ -53,7 +53,7 @@ module Register_backend(M : Backend) = struct
       match t with
       | Too_many_backends backends ->
         Loc.exnf loc
-          "Too many independant %s found:\n%s"
+          "Too many independent %s found:\n%s"
           (M.desc ~plural:true)
           (String.concat ~sep:"\n"
              (List.map backends ~f:(fun t ->

src/sub_system_intf.ml

@@ -60,7 +60,7 @@ module type Registered_backend = sig
 
       The returned list is sorted by order of dependencies. It is not
       allowed to have two different backend that are completely
-      independant, i.e. none of them is in the transitive closure of
+      independent, i.e. none of them is in the transitive closure of
       the other one. *)
   val select_extensible_backends
     :  ?written_by_user:t list

test/README.md

@@ -30,7 +30,7 @@ variable and use it.
 
 Test cases are in `blackbox-tests/test-cases`. Each sub-directory is a
 full blown jbuilder project. Each sub-directory contains a `run.t`
-file, which represent a few invokation of jbuilder along with the
+file, which represents a few invocations of jbuilder along with the
 expected output.
 
 Here is a sample `.t` file:

test/blackbox-tests/test-cases/configurator/run.t

@@ -3,7 +3,7 @@ Show that config values are present
   DUNE_CONFIGURATOR is present
   version is present
 
-We're able to compile C program sucessfully
+We're able to compile C program successfully
   $ dune exec c_test/run.exe
   Successfully compiled c program
 

test/blackbox-tests/test-cases/inline_tests/run.t

@@ -11,7 +11,7 @@
 
   $ dune runtest too-many-backends
   File "too-many-backends/dune", line 17, characters 1-15:
-  Error: Too many independant inline tests backends found:
+  Error: Too many independent inline tests backends found:
   - "backend_tmb1" in _build/default/too-many-backends
   - "backend_tmb2" in _build/default/too-many-backends
   [1]