no bug - fix spelling of 'mozila' tree-wide r=me
authorWes Kocher <wkocher@mozilla.com>
Mon, 18 Mar 2019 15:55:18 -0700
changeset 464919 2c2dd59df579888dd52057037d468cab5c316a56
parent 464918 6ed5e5a3e39ec3155a2a36f4d567e927df3a6f39
child 464920 7a76a71448ff98dd6705f38dda0ad06a6da9e032
push id35728
push userdvarga@mozilla.com
push dateTue, 19 Mar 2019 09:50:54 +0000
treeherdermozilla-central@880331515823 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersme
milestone68.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
no bug - fix spelling of 'mozila' tree-wide r=me
build/mozconfig.comm-support
testing/geckodriver/doc/TraceLogs.md
--- a/build/mozconfig.comm-support
+++ b/build/mozconfig.comm-support
@@ -22,17 +22,17 @@
 if [ "$(dirname "$2")" = "$topsrcdir" ]; then
   # No weirdness
   if [ -d "$topsrcdir/mail" ]; then
     # Building with comm-central as top-level directory.
     echo "ERROR: Should not include mozilla/build/mozconfig.comm when building"
     echo "       with comm-central as top-level directory."
     exit 1
   elif [ -d "$topsrcdir/comm/mail" ]; then
-    # Building with mozila-central as top-level directory.
+    # Building with mozilla-central as top-level directory.
     . "$topsrcdir/comm/build/mozconfig.comm-support"
   else
     echo "ERROR: Unknown build directory layout."
     exit 1
   fi
 elif [ "$(dirname "$2")" = "$(dirname "$topsrcdir")" ]; then
   if [ -d "$topsrcdir/../mail" ]; then
     # Building with comm-central as top-level directory;
--- a/testing/geckodriver/doc/TraceLogs.md
+++ b/testing/geckodriver/doc/TraceLogs.md
@@ -66,17 +66,17 @@ The log level is set in different ways. 
 `--log <LEVEL>` option, where `LEVEL` is one of the log levels
 from the list above, or by using the `-v` (for debug) or `-vv`
 (for trace) shorthands.  For example, the following command will
 enable trace logs for both geckodriver and Marionette:
 
 	% geckodriver -vv
 
 The second way of setting the log level is through capabilities.
-geckodriver accepts a Mozila-specific configuration object
+geckodriver accepts a Mozilla-specific configuration object
 in [`moz:firefoxOptions`].  This JSON Object, which is further
 described in the [README] can hold Firefox-specific configuration,
 such as which Firefox binary to use, additional preferences to set,
 and of course which log level to use.
 
 [`moz:firefoxOptions`]: https://searchfox.org/mozilla-central/source/testing/geckodriver/README.md#firefox-capabilities
 [README]: https://searchfox.org/mozilla-central/source/testing/geckodriver/README.md