From 3608dc8457f2e622906bcd40162c4e6156efc17e Mon Sep 17 00:00:00 2001 From: Sylvestre Ledru Date: Thu, 19 Oct 2023 20:52:10 +0000 Subject: [PATCH] Bug 1860157 - Fix typos found by codespell 2.2.6 r=webdriver-reviewers,zeid,search-reviewers,perftest-reviewers,devtools-reviewers,releng-reviewers,gbrown,sparky,jteow Differential Revision: https://phabricator.services.mozilla.com/D191480 --- .../newtab/content-src/asrouter/docs/targeting-attributes.md | 2 +- .../components/newtab/docs/v2-system-addon/data_dictionary.md | 2 +- browser/installer/windows/docs/MSIX.rst | 2 +- browser/locales/en-US/browser/menubar.ftl | 2 +- browser/locales/en-US/browser/panelUI.ftl | 2 +- devtools/client/locales/en-US/filterwidget.properties | 2 +- .../docs/user/debugger/how_to/set_watch_expressions/index.rst | 2 +- docs/_static/sphinx_design.js | 2 +- docs/bug-mgmt/policies/triage-bugzilla.rst | 2 +- docs/bug-mgmt/processes/labels.rst | 2 +- .../coding-style/format_cpp_code_with_clang-format.rst | 2 +- docs/contributing/editors/vscode.rst | 2 +- docs/contributing/vcs/mercurial.rst | 2 +- docs/nspr/layeredpoll.rst | 4 ++-- docs/nspr/reference/i_o_functions.rst | 2 +- docs/nspr/reference/prdescidentity.rst | 2 +- docs/nspr/reference/prfileprivate.rst | 2 +- docs/nspr/reference/priomethods.rst | 2 +- docs/setup/building_with_debug_symbols.rst | 2 +- dom/docs/workersAndStorage/CodeStyle.rst | 2 +- dom/locales/en-US/chrome/dom/dom.properties | 2 +- gfx/docs/RenderingOverview.rst | 2 +- ipc/docs/ipdl.rst | 2 +- ipc/docs/processes.rst | 2 +- python/mozlint/test/test_cli.py | 2 +- remote/doc/cdp/Architecture.md | 2 +- taskcluster/docs/attributes.rst | 2 +- taskcluster/docs/cron.rst | 2 +- taskcluster/docs/partials.rst | 2 +- testing/geckodriver/doc/Bugs.md | 2 +- testing/mozbase/docs/manifestparser.rst | 2 +- toolkit/components/extensions/docs/schema.rst | 2 +- toolkit/components/search/docs/SearchConfigurationSchema.rst | 2 +- toolkit/components/telemetry/docs/collection/custom-pings.rst | 2 +- .../telemetry/docs/data/backgroundhangmonitor-ping.rst | 2 +- tools/lint/spell/exclude-list.txt | 2 ++ tools/profiler/docs/buffer.rst | 2 +- tools/sanitizer/docs/asan_nightly.rst | 2 +- tools/tryselect/docs/presets.rst | 2 +- tools/tryselect/lando.py | 2 +- tools/tryselect/selectors/perf.py | 2 +- xpcom/docs/xpidl.rst | 2 +- 42 files changed, 44 insertions(+), 42 deletions(-) diff --git a/browser/components/newtab/content-src/asrouter/docs/targeting-attributes.md b/browser/components/newtab/content-src/asrouter/docs/targeting-attributes.md index 848ce2b0c168..b7c58b41cb5e 100644 --- a/browser/components/newtab/content-src/asrouter/docs/targeting-attributes.md +++ b/browser/components/newtab/content-src/asrouter/docs/targeting-attributes.md @@ -4,7 +4,7 @@ When you create ASRouter messages such as snippets, contextual feature recommend Targeting information must be captured in [an expression](./targeting-guide.md) that has access to the following attributes. You may combine and compare any of these attributes as needed. -Please note that some targeting attributes require stricter controls on the telemetry than can be colleted, so when in doubt, ask for review. +Please note that some targeting attributes require stricter controls on the telemetry than can be collected, so when in doubt, ask for review. ## Available attributes diff --git a/browser/components/newtab/docs/v2-system-addon/data_dictionary.md b/browser/components/newtab/docs/v2-system-addon/data_dictionary.md index 35bb084f38b3..fe4c8411f96d 100644 --- a/browser/components/newtab/docs/v2-system-addon/data_dictionary.md +++ b/browser/components/newtab/docs/v2-system-addon/data_dictionary.md @@ -291,7 +291,7 @@ Schema definitions/validations that can be used for tests can be found in `syste +----------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+------------------+ | ``attribution.experiment`` | [Optional] Funnel experiment identifier, see bug 1567339 | :one: | +----------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+------------------+ -| ``attribution.variantion`` | [Optional] Funnel experiment variant identifier, see bug 1567339 | :one: | +| ``attribution.variation`` | [Optional] Funnel experiment variant identifier, see bug 1567339 | :one: | +----------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+------------------+ | ``attribution.ua`` | [Optional] Derived user agent, see bug 1595063 | :one: | +----------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------+------------------+ diff --git a/browser/installer/windows/docs/MSIX.rst b/browser/installer/windows/docs/MSIX.rst index ec73d1950c99..771ea6c061d7 100644 --- a/browser/installer/windows/docs/MSIX.rst +++ b/browser/installer/windows/docs/MSIX.rst @@ -164,7 +164,7 @@ Signing Certificates ^^^^^^^^^^^^^^^^^^^^ Mach will create the necessary signing keys and certificates for you -and re-use them for subsequent signings. Before your locally signed +and reuse them for subsequent signings. Before your locally signed builds can be installed you will need to install the correct certificate to the Windows Root Store. This can be done with a command like: diff --git a/browser/locales/en-US/browser/menubar.ftl b/browser/locales/en-US/browser/menubar.ftl index 57767232c6d4..6b5ae849ba66 100644 --- a/browser/locales/en-US/browser/menubar.ftl +++ b/browser/locales/en-US/browser/menubar.ftl @@ -5,7 +5,7 @@ # NOTE: For English locales, strings in this file should be in APA-style Title Case. # See https://apastyle.apa.org/style-grammar-guidelines/capitalization/title-case # -# NOTE: For Engineers, please don't re-use these strings outside of the menubar. +# NOTE: For Engineers, please don't reuse these strings outside of the menubar. ## Application Menu (macOS only) diff --git a/browser/locales/en-US/browser/panelUI.ftl b/browser/locales/en-US/browser/panelUI.ftl index 66acf049a962..617df7013e6a 100644 --- a/browser/locales/en-US/browser/panelUI.ftl +++ b/browser/locales/en-US/browser/panelUI.ftl @@ -17,7 +17,7 @@ customize-menu-add-to-overflowmenu = ## Forget Button -# The forget button can be added to the toolbar or overflow menu via the cutomization menu. +# The forget button can be added to the toolbar or overflow menu via the customization menu. panic-button-thankyou-msg1 = Your recent history is cleared. panic-button-thankyou-msg2 = Safe browsing! panic-button-thankyou-button = diff --git a/devtools/client/locales/en-US/filterwidget.properties b/devtools/client/locales/en-US/filterwidget.properties index ddd2f266501c..d777ab92ea2f 100644 --- a/devtools/client/locales/en-US/filterwidget.properties +++ b/devtools/client/locales/en-US/filterwidget.properties @@ -15,7 +15,7 @@ emptyFilterList=No filter specified # This string is displayed when preset's list is empty emptyPresetList=You don’t have any saved presets. \ You can store filter presets by choosing a name and saving them. \ -Presets are quickly accessible and you can re-use them with ease. +Presets are quickly accessible and you can reuse them with ease. # LOCALIZATION NOTE (addUsingList): # This string is displayed under [emptyFilterList] when filter's diff --git a/devtools/docs/user/debugger/how_to/set_watch_expressions/index.rst b/devtools/docs/user/debugger/how_to/set_watch_expressions/index.rst index e70de5391a62..db67729c59cd 100644 --- a/devtools/docs/user/debugger/how_to/set_watch_expressions/index.rst +++ b/devtools/docs/user/debugger/how_to/set_watch_expressions/index.rst @@ -12,7 +12,7 @@ The screenshot below shows the *Watch expressions* panel with a number of expres To add a watch expression click the **+** button in the top right corner of the panel. Then type the expression into the text entry field that appears at the bottom of the panel, and press :kbd:`Enter` to save it. The expression will be evaluated when you save, when you step through the code, or when you select the *Refresh* icon (next to **+**). -You can enter any valid expression into the watch, and even declare new "watch" variables and re-use them. For example, ``mywatchvar1 = 3`` and ``mywatchvar2 = mywatchvar1 + 2`` will evaluate ``mywatchvar2`` as 5. You can also declare an expression that modifies a variable value in the code, and this will be re-evaluated whenever you step through the code or refresh the watch expression. +You can enter any valid expression into the watch, and even declare new "watch" variables and reuse them. For example, ``mywatchvar1 = 3`` and ``mywatchvar2 = mywatchvar1 + 2`` will evaluate ``mywatchvar2`` as 5. You can also declare an expression that modifies a variable value in the code, and this will be re-evaluated whenever you step through the code or refresh the watch expression. .. warning:: diff --git a/docs/_static/sphinx_design.js b/docs/_static/sphinx_design.js index d080f2d634ab..260460bbcd89 100644 --- a/docs/_static/sphinx_design.js +++ b/docs/_static/sphinx_design.js @@ -55,7 +55,7 @@ } } - // Initiallize dropdown link + // Initialize dropdown link window.addEventListener("DOMContentLoaded", () => { if (document.getElementsByClassName(dropdownClassName).length) { setupDropdownLink(); diff --git a/docs/bug-mgmt/policies/triage-bugzilla.rst b/docs/bug-mgmt/policies/triage-bugzilla.rst index 0467b9964589..84812b97edcc 100644 --- a/docs/bug-mgmt/policies/triage-bugzilla.rst +++ b/docs/bug-mgmt/policies/triage-bugzilla.rst @@ -68,7 +68,7 @@ Firefox::General and Toolkit::General ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Bugs in Firefox::General are fitted with Bug Bug’s model to see if -there’s another component with a high liklihood of fit, and if a +there’s another component with a high likelihood of fit, and if a threshold confidence is achieved, the bug is moved to that component. Members of the community also review bugs in this component and try to diff --git a/docs/bug-mgmt/processes/labels.rst b/docs/bug-mgmt/processes/labels.rst index 9541d9da61e6..60c1bbeb2b46 100644 --- a/docs/bug-mgmt/processes/labels.rst +++ b/docs/bug-mgmt/processes/labels.rst @@ -8,7 +8,7 @@ conventions include: - Consistency makes measurement of processes simpler across the organization -- Consistency makes it easier to write re-usable process tools +- Consistency makes it easier to write reusable process tools - Consistency increases clarity for those than need to work across different repositories and bug trackers - Consistency reduces friction around engineering mobility between diff --git a/docs/code-quality/coding-style/format_cpp_code_with_clang-format.rst b/docs/code-quality/coding-style/format_cpp_code_with_clang-format.rst index ca64835410df..ce898149c58c 100644 --- a/docs/code-quality/coding-style/format_cpp_code_with_clang-format.rst +++ b/docs/code-quality/coding-style/format_cpp_code_with_clang-format.rst @@ -78,7 +78,7 @@ the ``--assume-filename `` argument. Configuring the clang-format commit hook ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -To run clang-format at commit phase, run ``mach boostrap`` or just add +To run clang-format at commit phase, run ``mach bootstrap`` or just add the following line in the ``hgrc`` file: .. code:: ini diff --git a/docs/contributing/editors/vscode.rst b/docs/contributing/editors/vscode.rst index d4a22f0b825c..e8c745342eff 100644 --- a/docs/contributing/editors/vscode.rst +++ b/docs/contributing/editors/vscode.rst @@ -31,7 +31,7 @@ Getting setup ------------- Close `VS Code` if it is already open, then build the configuration for `VS Code` -by simplying running from the terminal: +by simply running from the terminal: .. code:: diff --git a/docs/contributing/vcs/mercurial.rst b/docs/contributing/vcs/mercurial.rst index ef40bbee19ee..dc52b97e8ad4 100644 --- a/docs/contributing/vcs/mercurial.rst +++ b/docs/contributing/vcs/mercurial.rst @@ -156,7 +156,7 @@ to verify they are available on your build machine. Extensions ---------- -There's a number of extensions you can enable. See http://mercurial.selenic.com/wiki/UsingExtensions. Almost everyone should probably enable the following, most of them are enabled by ``mach boostrap``: +There's a number of extensions you can enable. See http://mercurial.selenic.com/wiki/UsingExtensions. Almost everyone should probably enable the following, most of them are enabled by ``mach bootstrap``: #. color - Colorize terminal output #. histedit - Provides git rebase --interactive behavior. diff --git a/docs/nspr/layeredpoll.rst b/docs/nspr/layeredpoll.rst index 6f5cb80efefc..f70c36fa6bd0 100644 --- a/docs/nspr/layeredpoll.rst +++ b/docs/nspr/layeredpoll.rst @@ -22,7 +22,7 @@ of the :ref:`PRPollDesc` array that has a non-NULL :ref:`PRFileDesc` and whose ``poll() method``. The ``poll()`` method is one of the vector contained in the :ref:`PRIOMethods` table. In the case of layered I/O, the elements (the -methods) of the methods table may be overridden by the implementor of +methods) of the methods table may be overridden by the implementer of that layer. The layers are then *stacked.* I/O using that *stack* will call through the method at the top layer, and each layer may make altering decisions regarding how the I/O operation should proceed. @@ -55,7 +55,7 @@ methods table. One can get a copy of default methods by calling :ref:`PR_GetDefaultIOMethods` These methods simply pass all calls through the layer on to the next lower layer of the stack. -A layer implementor might copy the elements of the ``PRIOMethods`` +A layer implementer might copy the elements of the ``PRIOMethods`` acquired from this function into a methods table of its own, then override just those methods of interest. *Usually* (with only a single exception) a layered method will perform its design duties and then call diff --git a/docs/nspr/reference/i_o_functions.rst b/docs/nspr/reference/i_o_functions.rst index a13d0b3b74e0..667f05d06f7f 100644 --- a/docs/nspr/reference/i_o_functions.rst +++ b/docs/nspr/reference/i_o_functions.rst @@ -200,7 +200,7 @@ File descriptors may be layered. For example, SSL is a layer on top of a reliable bytestream layer such as TCP. Each type of layer has a unique identity, which is allocated by the -runtime. The layer implementor should associate the identity with all +runtime. The layer implementer should associate the identity with all layers of that type. It is then possible to scan the chain of layers and find a layer that one recognizes and therefore predict that it will implement a desired protocol. diff --git a/docs/nspr/reference/prdescidentity.rst b/docs/nspr/reference/prdescidentity.rst index 9f9ad2767fe4..da900f37a783 100644 --- a/docs/nspr/reference/prdescidentity.rst +++ b/docs/nspr/reference/prdescidentity.rst @@ -19,7 +19,7 @@ Description File descriptors may be layered. Each layer has it own identity. Identities are allocated by the runtime and are to be associated (by the -layer implementor) with all file descriptors of that layer. It is then +layer implementer) with all file descriptors of that layer. It is then possible to scan the chain of layers and find a layer that one recognizes, then predict that it will implement a desired protocol. diff --git a/docs/nspr/reference/prfileprivate.rst b/docs/nspr/reference/prfileprivate.rst index dc264d7d8558..4fa215d9d3b6 100644 --- a/docs/nspr/reference/prfileprivate.rst +++ b/docs/nspr/reference/prfileprivate.rst @@ -18,7 +18,7 @@ Syntax Description ----------- -A layer implementor should collect all the private data of the layer in +A layer implementer should collect all the private data of the layer in the :ref:`PRFilePrivate` structure. Each layer has its own definition of :ref:`PRFilePrivate`, which is hidden from other layers as well as from the users of the layer. diff --git a/docs/nspr/reference/priomethods.rst b/docs/nspr/reference/priomethods.rst index 8e50ae17817d..127c64f54340 100644 --- a/docs/nspr/reference/priomethods.rst +++ b/docs/nspr/reference/priomethods.rst @@ -118,7 +118,7 @@ implements the :ref:`PR_Write` function. For type definition details, see ``prio.h``. The I/O methods table provides procedural access to the functions of the -file descriptor. It is the responsibility of a layer implementor to +file descriptor. It is the responsibility of a layer implementer to provide suitable functions at every entry point (that is, for every function in the I/O methods table). If a layer provides no functionality, it should call the next lower (higher) function of the diff --git a/docs/setup/building_with_debug_symbols.rst b/docs/setup/building_with_debug_symbols.rst index 316e04af314a..596bd9010b23 100644 --- a/docs/setup/building_with_debug_symbols.rst +++ b/docs/setup/building_with_debug_symbols.rst @@ -17,7 +17,7 @@ Building Firefox with symbols ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ There is a single configure option to enable building with symbols on -all platforms. This is enabled by default so unless you have explcitly +all platforms. This is enabled by default so unless you have explicitly disabled it your build you should include symbols. :: diff --git a/dom/docs/workersAndStorage/CodeStyle.rst b/dom/docs/workersAndStorage/CodeStyle.rst index 822779d179b0..ef5e6e13b57c 100644 --- a/dom/docs/workersAndStorage/CodeStyle.rst +++ b/dom/docs/workersAndStorage/CodeStyle.rst @@ -60,7 +60,7 @@ Deviations from the Mozilla C++ Coding Style | Mozilla style | Prevalent WAS style | Deviation scope | Evolution | +========================================================================================================+============================================================================================+=================+=====================================================================================+ | We prefer using "static", instead of anonymous C++ namespaces. | Place all symbols that should have internal linkage in a single anonymous | All files | Unclear. The recommendation in the Mozilla code style says this might change in the | -| | namespace block at the top of an implementation file, rather than declarating them static. | | future depending on debugger support, so this deviation might become obsolete. | +| | namespace block at the top of an implementation file, rather than declaring them static. | | future depending on debugger support, so this deviation might become obsolete. | | | | | | +--------------------------------------------------------------------------------------------------------+--------------------------------------------------------------------------------------------+-----------------+-------------------------------------------------------------------------------------+ | `All parameters passed by lvalue reference must be labeled const. [...] Input parameters may be const | Non-const reference parameters may be used. | All files | Unclear. Maybe at least restrict the use of non-const reference parameters to | diff --git a/dom/locales/en-US/chrome/dom/dom.properties b/dom/locales/en-US/chrome/dom/dom.properties index 300d91974325..e1192a016c95 100644 --- a/dom/locales/en-US/chrome/dom/dom.properties +++ b/dom/locales/en-US/chrome/dom/dom.properties @@ -354,7 +354,7 @@ AllEntryTypesIgnored=No valid entryTypes; aborting registration. # LOCALIZATION NOTE: do not localize key=“%S” modifiers=“%S” id=“%S” GTK2Conflict2=Key event not available on GTK2: key=“%S” modifiers=“%S” id=“%S” WinConflict2=Key event not available on some keyboard layouts: key=“%S” modifiers=“%S” id=“%S” -# LOCALIZATION NOTE: do not trnaslated "document.domain" +# LOCALIZATION NOTE: do not translated "document.domain" DocumentSetDomainNotAllowedWarning=Setting document.domain in a cross-origin isolated environment is not allowed. #LOCALIZATION NOTE(DeprecatedTestingInterfaceWarning): Do not translate this message. It's just testing only. diff --git a/gfx/docs/RenderingOverview.rst b/gfx/docs/RenderingOverview.rst index 50b146d9b951..1b2e30b6f63b 100644 --- a/gfx/docs/RenderingOverview.rst +++ b/gfx/docs/RenderingOverview.rst @@ -348,7 +348,7 @@ equivalent of layers is Slices -- a grouping of pictures that are expected to render and update together. Slices are automatically created based on heuristics and layout hints/flags. -Implementation wise, slices re-use a lot of the existing machinery for Pictures; +Implementation wise, slices reuse a lot of the existing machinery for Pictures; in fact they're implemented as a "Virtual picture" of sorts. The similarities make sense: both need to allocate offscreen textures in a cache, both will position and render all their children into it, and both then draw themselves diff --git a/ipc/docs/ipdl.rst b/ipc/docs/ipdl.rst index 422f5c490304..1491d2bdc490 100644 --- a/ipc/docs/ipdl.rst +++ b/ipc/docs/ipdl.rst @@ -55,7 +55,7 @@ just needs endpoints to be bound judiciously at runtime. The example in :ref:`Connecting With Other Processes` shows one way this can be done. It also shows that, without proper plain-language documentation of *all* of the ways endpoints are configured, this can quickly lead to unmaintainable code. -Be sure to document your endpoint bindings throroughly!!! +Be sure to document your endpoint bindings thoroughly!!! .. _Chromium Mojo: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/mojo/core/README.md#Port diff --git a/ipc/docs/processes.rst b/ipc/docs/processes.rst index b13815d24453..b9c3cb263d1d 100644 --- a/ipc/docs/processes.rst +++ b/ipc/docs/processes.rst @@ -502,7 +502,7 @@ _____________ + ``MacSandboxInfo::AppendAsParams()`` in the `switch statement `_ - + ``StartMacSandbox()`` in the `serie of if/else statements + + ``StartMacSandbox()`` in the `series of if/else statements `_. This code sets template values for the sandbox string rendering, and is running on the side of the main process. diff --git a/python/mozlint/test/test_cli.py b/python/mozlint/test/test_cli.py index 2ad12596ebf2..4e9219a2ead6 100644 --- a/python/mozlint/test/test_cli.py +++ b/python/mozlint/test/test_cli.py @@ -115,7 +115,7 @@ def test_cli_run_with_wrong_linters(run, capfd): run(["-l", "external", "-l", "foobar"]) out, err = capfd.readouterr() - # Check if it identifes foobar as invalid linter + # Check if it identifies foobar as invalid linter assert "A failure occurred in the foobar linter." in out # Check for exception message diff --git a/remote/doc/cdp/Architecture.md b/remote/doc/cdp/Architecture.md index f9465e3c71ed..87f4f8d524d4 100644 --- a/remote/doc/cdp/Architecture.md +++ b/remote/doc/cdp/Architecture.md @@ -99,7 +99,7 @@ Then, there is two ways to communicate with the other targets: * Use `Target.attachToTarget({ flatten: true })` and include `sessionId` in CDP packets This requires a special client, which will use the `sessionId` returned by `Target.attachToTarget()` in order to spawn a distinct client instance. - This client will re-use the same WebSocket connection, but every single CDP packet will contain an additional `sessionId` attribute. + This client will reuse the same WebSocket connection, but every single CDP packet will contain an additional `sessionId` attribute. This helps distinguish packets which relate to the original target as well as the multiple additional targets you may attach to. In both cases, `Target.attachToTarget()` is special as it will spawn `cdp/session/TabSession` for the tab you are attaching to. diff --git a/taskcluster/docs/attributes.rst b/taskcluster/docs/attributes.rst index 5d187c2e9a1a..c3d5daabf9db 100644 --- a/taskcluster/docs/attributes.rst +++ b/taskcluster/docs/attributes.rst @@ -257,7 +257,7 @@ toolchain-command ================= An extra attribute used to communicate to the build system bootstrap code the command used to build the toolchain. This is useful because the commands are -formatted differently depending on the worker type, sometimes unconveniently +formatted differently depending on the worker type, sometimes inconveniently to parse afterwards. always_target diff --git a/taskcluster/docs/cron.rst b/taskcluster/docs/cron.rst index 86552114c167..8c1aaed6d19f 100644 --- a/taskcluster/docs/cron.rst +++ b/taskcluster/docs/cron.rst @@ -11,7 +11,7 @@ In the root of the Gecko directory, you will find `.cron.yml`. This defines the periodic tasks ("cron jobs") run for Gecko. Each specifies a name, what to do, and some parameters to determine when the cron job should occur. -See `the scema `_ +See `the schema `_ for details on the format and meaning of this file. How It Works diff --git a/taskcluster/docs/partials.rst b/taskcluster/docs/partials.rst index e4cb36935488..c0aeca1c3c3f 100644 --- a/taskcluster/docs/partials.rst +++ b/taskcluster/docs/partials.rst @@ -53,7 +53,7 @@ scan the 'from_mar' and 'to_mar', download the tools, and run ``make_incremental ``tools/update-packaging``. If a scope is given for a set of temporary S3 credentials, the task will use a caching script, -to allow re-use of the diffs made for larger files. Some of the larger files are not localised, +to allow reuse of the diffs made for larger files. Some of the larger files are not localised, and this allows us to save a lot of compute time. For Releases diff --git a/testing/geckodriver/doc/Bugs.md b/testing/geckodriver/doc/Bugs.md index b561bd41b584..4c1b955c3ecc 100644 --- a/testing/geckodriver/doc/Bugs.md +++ b/testing/geckodriver/doc/Bugs.md @@ -12,7 +12,7 @@ useful thing to provide is a minimal HTML document which permits the problem to be reproduced along with a [trace-level log] from geckodriver showing the exact wire protocol calls made. -Because of the wide variety and different charateristics of clients +Because of the wide variety and different characteristics of clients used with geckodriver, their stacktraces, logs, and code examples are typically not very useful as they distract from the actual underlying cause. **For this reason, we cannot overstate the importance of diff --git a/testing/mozbase/docs/manifestparser.rst b/testing/mozbase/docs/manifestparser.rst index f4bff9154f18..5441ac6c46b4 100644 --- a/testing/mozbase/docs/manifestparser.rst +++ b/testing/mozbase/docs/manifestparser.rst @@ -522,7 +522,7 @@ through several design considerations. programmatically editable. While the ``*.ini`` format worked for a long time the underspecified syntax made it difficult to reliably parse. The new ``*.toml`` format is widely accepted, as a formal syntax as well - as libararies to read and edit it (e.g. ``tomlkit``). + as libraries to read and edit it (e.g. ``tomlkit``). * there should be a single file that may easily be transported. Traditionally, test harnesses have lived in diff --git a/toolkit/components/extensions/docs/schema.rst b/toolkit/components/extensions/docs/schema.rst index b55e9185884e..522328b4ec2c 100644 --- a/toolkit/components/extensions/docs/schema.rst +++ b/toolkit/components/extensions/docs/schema.rst @@ -60,7 +60,7 @@ Declarations within a namespace look like: The four types of objects that can be defined inside a namespace are: -- **types**: A type is a re-usable schema fragment. A common use of types +- **types**: A type is a reusable schema fragment. A common use of types is to define in one place an object with a particular set of typed fields that is used in multiple places in an API. diff --git a/toolkit/components/search/docs/SearchConfigurationSchema.rst b/toolkit/components/search/docs/SearchConfigurationSchema.rst index 9ba5a3cf57e8..b57f69fe1386 100644 --- a/toolkit/components/search/docs/SearchConfigurationSchema.rst +++ b/toolkit/components/search/docs/SearchConfigurationSchema.rst @@ -535,7 +535,7 @@ In this example, for normal mode: In private browsing mode: - - engine1@ext is default in the US region, and all other regions execpt for GB and FR + - engine1@ext is default in the US region, and all other regions except for GB and FR - engine2@ext is default in only the GB region - engine3@ext is never default anywhere - engine4@ext is default in the FR region. diff --git a/toolkit/components/telemetry/docs/collection/custom-pings.rst b/toolkit/components/telemetry/docs/collection/custom-pings.rst index 395a23aace95..fc1fd5a5ac4f 100644 --- a/toolkit/components/telemetry/docs/collection/custom-pings.rst +++ b/toolkit/components/telemetry/docs/collection/custom-pings.rst @@ -77,4 +77,4 @@ In addition to the `data collection review `__. As the report will usually not include any steps to reproduce or a test case, it will most likely receive a lower-end bounty. Like with regular -bug reports, we would typically reward the first (identifable) report of +bug reports, we would typically reward the first (identifiable) report of an issue. .. warning:: diff --git a/tools/tryselect/docs/presets.rst b/tools/tryselect/docs/presets.rst index 6e1008a4565f..a3368cf8b555 100644 --- a/tools/tryselect/docs/presets.rst +++ b/tools/tryselect/docs/presets.rst @@ -2,7 +2,7 @@ Presets ======= Some selectors, such as ``fuzzy`` and ``syntax``, allow saving and loading presets from a file. This is a -good way to re-use a selection, either at a later date or by sharing with others. Look for a +good way to reuse a selection, either at a later date or by sharing with others. Look for a 'preset' section in ``mach --help`` to determine whether the selector supports this functionality. diff --git a/tools/tryselect/lando.py b/tools/tryselect/lando.py index 899a0baa9dde..d69f6d77f904 100644 --- a/tools/tryselect/lando.py +++ b/tools/tryselect/lando.py @@ -82,7 +82,7 @@ def get_stack_info(vcs: SupportedVcsRepository) -> Tuple[str, List[str]]: ) print("Using", base_commit, "as the hg base commit.") - # Re-use the base revision when on Mercurial to avoid multiple calls to `hg log`. + # Reuse the base revision when on Mercurial to avoid multiple calls to `hg log`. branch_nodes_kwargs = {} if isinstance(vcs, HgRepository): branch_nodes_kwargs["base_ref"] = base_commit diff --git a/tools/tryselect/selectors/perf.py b/tools/tryselect/selectors/perf.py index 3126f57118bb..9d4889cd9d25 100644 --- a/tools/tryselect/selectors/perf.py +++ b/tools/tryselect/selectors/perf.py @@ -717,7 +717,7 @@ class PerfParser(CompareParser): # a platform. This means categories with mixed suites will # be available even if some suites will no longer run # given this platform constraint. The reasoning for this is that - # it's unexpected to receive desktop tests when you explcitly + # it's unexpected to receive desktop tests when you explicitly # request android. platform_queries = { suite: ( diff --git a/xpcom/docs/xpidl.rst b/xpcom/docs/xpidl.rst index 86bf9180f20e..1430ba63761c 100644 --- a/xpcom/docs/xpidl.rst +++ b/xpcom/docs/xpidl.rst @@ -340,7 +340,7 @@ properties they may have. The ``array`` property turns the parameter into an arr the parameter must also have a corresponding ``size_is`` property whose argument is the parameter that has the size of the array. In native code, the type gains another pointer indirection, and JavaScript arrays are used in script code. -Script code callers can ignore the value of array parameter, but implementors +Script code callers can ignore the value of array parameter, but implementers must still set the values appropriately. .. note::