Bug 1496903 - Fix the typos found by codespell 1.14 r=ahal
authorSylvestre Ledru <sledru@mozilla.com>
Tue, 09 Oct 2018 14:31:39 +0000
changeset 498711 367c440ef7f7c490d0f845230afccac57f187646
parent 498710 272ae7de4168019cee0c4c59a93f33293728618c
child 498712 679d009963f936849de348afb08098a0702f148d
push id1864
push userffxbld-merge
push dateMon, 03 Dec 2018 15:51:40 +0000
treeherdermozilla-release@f040763d99ad [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersahal
bugs1496903
milestone64.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
Bug 1496903 - Fix the typos found by codespell 1.14 r=ahal Depends on D7958 Differential Revision: https://phabricator.services.mozilla.com/D7959
build/docs/mozbuild-files.rst
toolkit/components/telemetry/docs/collection/scalars.rst
toolkit/components/telemetry/docs/collection/stack-capture.rst
toolkit/components/telemetry/docs/data/main-ping.rst
--- a/build/docs/mozbuild-files.rst
+++ b/build/docs/mozbuild-files.rst
@@ -142,17 +142,17 @@ Filesystem reading mode is utilized to p
 Technical Details
 -----------------
 
 The code for reading ``moz.build`` files lives in
 :py:mod:`mozbuild.frontend.reader`. The Python sandboxes evaluation results
 (:py:class:`mozbuild.frontend.context.Context`) are passed into
 :py:mod:`mozbuild.frontend.emitter`, which converts them to classes defined
 in :py:mod:`mozbuild.frontend.data`. Each class in this module defines a
-domain-specific component of tree metdata. e.g. there will be separate
+domain-specific component of tree metadata. e.g. there will be separate
 classes that represent a JavaScript file vs a compiled C++ file or test
 manifests. This means downstream consumers of this data can filter on class
 types to only consume what they are interested in.
 
 There is no well-defined mapping between ``moz.build`` file instances
 and the number of :py:mod:`mozbuild.frontend.data` classes derived from
 each. Depending on the content of the ``moz.build`` file, there may be 1
 object derived or 100.
--- a/toolkit/components/telemetry/docs/collection/scalars.rst
+++ b/toolkit/components/telemetry/docs/collection/scalars.rst
@@ -122,18 +122,18 @@ The probes in the definition file are re
         kind: int
         ...
 
 .. _scalar-limitations:
 
 Category and probe names need to follow a few rules:
 
 - they cannot exceed 40 characters each;
-- category names must be alpha-numeric + ``.``, with no leading/trailing digit or ``.``;
-- probe names must be alpha-numeric + ``_``, with no leading/trailing digit or ``_``.
+- category names must be alphanumeric + ``.``, with no leading/trailing digit or ``.``;
+- probe names must be alphanumeric + ``_``, with no leading/trailing digit or ``_``.
 
 A probe can be defined as follows:
 
 .. code-block:: yaml
 
     a.category.hierarchy:
       a_scalar:
         bug_numbers:
--- a/toolkit/components/telemetry/docs/collection/stack-capture.rst
+++ b/toolkit/components/telemetry/docs/collection/stack-capture.rst
@@ -55,12 +55,12 @@ The behavior of ``CaptureStack`` is iden
 
 Limits and restrictions
 -----------------------
 Keys used for capturing stacks are meant to be unique among API users. Detection
 of collisions, however, is left to the users themselves. In its current implementation
 the API does not provide any means for key registration.
 
 To prevent abuses, the content of a key is limited to 50 characters in length.
-Additionally, keys may only contain alpha-numeric characters or ``-``.
+Additionally, keys may only contain alphanumeric characters or ``-``.
 
 Both the depth of the captured stacks and the total number of keys in the
 dictionary are limited to ``50``.
--- a/toolkit/components/telemetry/docs/data/main-ping.rst
+++ b/toolkit/components/telemetry/docs/data/main-ping.rst
@@ -294,17 +294,17 @@ information see :doc:`stack capture <../
 
 This is similar to :ref:`chromeHangs`, but only Precise C++ stacks on the main thread of
 the parent process are reported. This data is only available on Windows, either
 in Firefox Nightly or in builds using ``--enable-profiling`` switch.
 
 Limits for captured stacks are the same as for chromeHangs (see below). Furthermore:
 
 * the key length is limited to 50 characters,
-* keys are restricted to alpha-numeric characters and `-`.
+* keys are restricted to alphanumeric characters and `-`.
 
 The module names can contain unicode characters.
 
 Structure:
 
 .. code-block:: js
 
     "capturedStacks" : {