Correct spelling errors throughout the project (ocaml#9930)

Signed-off-by: Jakub Polak <[email protected]>
Co-authored-by: Etienne Millon <[email protected]>

Author: kupolak

bin/describe/aliases_targets.ml

@@ -123,7 +123,7 @@ module Targets_cmd = struct
       match Path.Build.equal (Path.Build.parent_exn path) dir with
       | false -> None
       | true ->
-        (* directory targets can be distinguied by the trailing path seperator
+        (* directory targets can be distinguied by the trailing path separator
         *)
         Some
           (match kind with

bin/describe/aliases_targets.mli

@@ -4,12 +4,12 @@ open Import
 
 module Aliases_cmd : sig
   (** The aliases command lists all the aliases available in the given
-      directory, defaulting to the current working direcctory. *)
+      directory, defaulting to the current working directory. *)
   val command : unit Cmd.t
 end
 
 module Targets_cmd : sig
   (** The targets command lists all the targets available in the given
-      directory, defaulting to the current working direcctory. *)
+      directory, defaulting to the current working directory. *)
   val command : unit Cmd.t
 end

bin/describe/describe_lang_compat.mli

@@ -1,4 +1,4 @@
-(** Dune describe commands used to take a --lang arugment that did nothing
+(** Dune describe commands used to take a --lang argument that did nothing
     expect for dune describe workspace. To keep compatilbility with accepting
     such an argument we provide a dummy argument here that can be used. It's
     value will typically be ignored. *)

bin/ocaml/doc.ml

@@ -6,7 +6,7 @@ let doc = "Build and view the documentation of an OCaml project"
 let man =
   [ `S "DESCRIPTION"
   ; `P
-      {|$(b,dune ocaml doc) builds and then opens the documention of an OCaml project in the users default browser.|}
+      {|$(b,dune ocaml doc) builds and then opens the documentation of an OCaml project in the users default browser.|}
   ; `Blocks Common.help_secs
   ]
 ;;

bin/pkg/pkg_common.mli

@@ -56,7 +56,7 @@ module Lock_dirs_arg : sig
       [Lock_dirs_arg.lock_dirs_of_workspace].
 
       There are two mutually exclusive cases:
-      - The user passed a list of lick directories as positonal
+      - The user passed a list of lick directories as positional
         arguments.contents
       - The user passed the ["--all"] flag, in which case all lock directories
         of the workspace are considered. *)
@@ -73,6 +73,6 @@ module Lock_dirs_arg : sig
   val lock_dirs_of_workspace : t -> Workspace.t -> Path.Source.t list
 end
 
-(** [pp_packages lock_dir] returns a list of pretty-printed packages occuring in
+(** [pp_packages lock_dir] returns a list of pretty-printed packages occurring in
     [lock_dir]. *)
 val pp_packages : Dune_pkg.Lock_dir.Pkg.t list -> 'a Pp.t

bin/rpc/rpc_common.mli

@@ -4,7 +4,7 @@ val active_server : unit -> Dune_rpc_private.Where.t
 (** Raise an RPC response error. *)
 val raise_rpc_error : Dune_rpc_private.Response.Error.t -> 'a
 
-(** Make a request and raise an exception if the preperation for the request
+(** Make a request and raise an exception if the preparation for the request
     fails in any way. Returns an [Error] if the response errors. *)
 val request_exn
   :  Dune_rpc_client.Client.t

bin/rpc/status.mli

@@ -1,2 +1,2 @@
-(** dune rpc status comamnd *)
+(** dune rpc status command *)
 val cmd : unit Cmdliner.Cmd.t

doc/coq.rst

@@ -116,7 +116,7 @@ The semantics of the fields are:
 
 - ``<coqdoc_flags>`` are extra user-configurable flags passed to ``coqdoc``. The
   default value for ``:standard`` is ``--toc``. The ``--html`` or ``--latex``
-  flags are passed separately depending on which mode is targed. See the section
+  flags are passed separately depending on which mode is target. See the section
   on :ref:`documentation using coqdoc<coqdoc>` for more information.
 
 - ``<stdlib_included>`` can either be ``yes`` or ``no``, currently defaulting to

doc/dev/rev-store.md

@@ -8,7 +8,7 @@ The Concepts
 ------------
 
 The revision store uses Git in the way of its original slogan, as a
-content-adressable file system. A lot of data (code) and meta-data (opam files)
+content-addressable file system. A lot of data (code) and meta-data (opam files)
 is stored in Git repositories that are often forked from each other, hence to
 save space Dune has a Git object cache.
 
@@ -47,7 +47,7 @@ background. The store should always work like a cache that can be discarded
 safely without causing data loss.
 
 The revision store should always give out the most recent version of data,
-unless explicitely instructed otherwise. This means that :
+unless explicitly instructed otherwise. This means that :
 
   * If only a Git source is specified, then the revision store will
     automatically get the newest revision
@@ -68,7 +68,7 @@ Support for other kinds of VCSes is a possible extension by replicating similar
 concepts with other version control systems, provided they allow for similar
 flexibility as the Git way of storing revisions. However at the moment most
 users have settled on using Git, hence this version should be able to
-accomodate the needs for most users.
+accommodate the needs for most users.
 
 Another compromise is that old repositories with long histories and large sizes
 have to be cloned before use, thus increasing the size of the initial download
@@ -97,7 +97,7 @@ one particular revision would be a waste of disk space as the Git tooling can
 be used to construct any revisions out of the bare repository anyway.
 
 Thus every source that is added to the revision store as a remote that tracks
-the default branch (or, if a branch is specified explicitely, then that
+the default branch (or, if a branch is specified explicitly, then that
 branch) and fetched, thus storing the required revisions in the revision store.
 
 The implementation of these features is a mix of calling the `git` binary and

doc/dev/rule-production.md

@@ -22,7 +22,7 @@ As we work on Dune, we expect that `dune_engine` will become more and
 more agnostic. Even though it is not completely agnostic, we have
 successfully been using it to build Jane Street code base, using the
 Jane Street rules on top of this core. So it's already more general
-than Dune iself.
+than Dune itself.
 
 For the purpose of this design doc, we will treat `dune_engine` as a
 completely general library that doesn't know about `dune` files.