Fix trivial spelling mistake in docs

Changed files
+4 -4
doc
nixos
doc
+1 -1
doc/release-notes.xml
···
<literal>stdenv</literal>; the formed changes the C compiler, and
the latter adds additional packages to the front of
<literal>stdenv</literal>’s initial <envar>PATH</envar>, allowing
-
tools to be overriden.</para>
+
tools to be overridden.</para>
<para>For instance, the package <varname>strategoxt</varname>
doesn’t build with the GNU Make in <literal>stdenv</literal>
+2 -2
doc/stdenv.xml
···
<para>Often it is necessary to override or modify some aspect of the
build. To make this easier, the standard environment breaks the
package build into a number of <emphasis>phases</emphasis>, all of
-
which can be overriden or modified individually: unpacking the
+
which can be overridden or modified individually: unpacking the
sources, applying patches, configuring, building, and installing.
(There are some others; see <xref linkend="ssec-stdenv-phases"/>.)
For instance, a package that doesn’t supply a makefile but instead has
···
the binaries). Furthermore, it allows a nicer presentation of build
logs in the Nix build farm.</para>
-
<para>Each phase can be overriden in its entirety either by setting
+
<para>Each phase can be overridden in its entirety either by setting
the environment variable
<varname><replaceable>name</replaceable>Phase</varname> to a string
containing some shell commands to be executed, or by redefining the
+1 -1
nixos/doc/manual/configuration.xml
···
be passed your customised instance. (However, the value
<literal>pkgs.emacs</literal> in
<varname>nixpkgs.config.packageOverrides</varname> refers to the
-
original rather than overriden instance, to prevent an infinite
+
original rather than overridden instance, to prevent an infinite
recursion.)</para>
</section>