Commit 128c74ca authored by Sylvestre Ledru's avatar Sylvestre Ledru
Browse files

Bug 1785451 - Ride along: Fix some typos... 

Bug 1785451 - Ride along: Fix some typos r=linter-reviewers,fluent-reviewers,geckoview-reviewers,extension-reviewers,keeler,rpl,calu,ahal,flod DONTBUILD

Differential Revision: https://phabricator.services.mozilla.com/D154946
parent da1e6e21

browser/components/newtab/docs/v2-system-addon/data_events.md

+1 −1
Original line number Diff line number Diff line
@@ -2,7 +2,7 @@ 


By default, the about:newtab, about:welcome and about:home pages in Firefox (the pages you see when you open a new tab and when you start the browser), will send data back to Mozilla servers about usage of these pages.  The intent is to collect data in order to improve the user's experience while using Activity Stream.  Data about your specific browsing behaior or the sites you visit is **never transmitted to any Mozilla server**.  At any time, it is easy to **turn off** this data collection by [opting out of Firefox telemetry](https://support.mozilla.org/kb/share-telemetry-data-mozilla-help-improve-firefox).



Data is sent to our servers in the form of discreet HTTPS 'pings' or messages whenever you do some action on the Activity Stream about:home, about:newtab or about:welcome pages.  We try to minimize the amount and frequency of pings by batching them together.  Pings are sent in [JSON serialized format](http://www.json.org/).

Data is sent to our servers in the form of discrete HTTPS 'pings' or messages whenever you do some action on the Activity Stream about:home, about:newtab or about:welcome pages.  We try to minimize the amount and frequency of pings by batching them together.  Pings are sent in [JSON serialized format](http://www.json.org/).



At Mozilla, [we take your privacy very seriously](https://www.mozilla.org/privacy/).  The Activity Stream page will never send any data that could personally identify you.  We do not transmit what you are browsing, searches you perform or any private settings.  Activity Stream does not set or send cookies, and uses [Transport Layer Security](https://en.wikipedia.org/wiki/Transport_Layer_Security) to securely transmit data to Mozilla servers.

devtools/client/locales/en-US/accessibility.ftl

+1 −1
Original line number Diff line number Diff line
@@ -10,7 +10,7 @@ accessibility-text-label-header = Text Labels and Names 


accessibility-keyboard-header = Keyboard



## Text entries that are used as text alternative for icons that depict accessibility isses.

## Text entries that are used as text alternative for icons that depict accessibility issues.



accessibility-warning =

  .alt = Warning

docs/performance/jit_profiling_with_perf.md

+1 −1
Original line number Diff line number Diff line
@@ -55,7 +55,7 @@ View the profile: 
perf report --no-children -i jit.data

```



All of the above comands can be put into a single shell script.

All of the above commands can be put into a single shell script.



### Profiling the Browser

mobile/android/docs/geckoview/contributor/geckoview-architecture.rst

+1 −1
Original line number Diff line number Diff line
@@ -769,7 +769,7 @@ whenever a password element is added to the DOM after the ``pageshow`` event. 
Prefs

-----



`Preferences </modules/libpref/index.html>`_ (or prefs) are used throughtout

`Preferences </modules/libpref/index.html>`_ (or prefs) are used throughout

Gecko to configure the browser, enable custom features, etc.



GeckoView does not directly expose prefs to Apps. A limited set configuration

toolkit/components/extensions/docs/lifecycle.rst

+1 −1
Original line number Diff line number Diff line
@@ -54,7 +54,7 @@ Note that these events can be triggered on extensions that are inactive. 
For that reason, these events can only be handled by extension APIs that

are built into the browser.  Or, in other words, these events cannot be

handled by APIs that are implemented in WebExtension experiments.  If the

implementation of an API relies on these events for corectness, the API

implementation of an API relies on these events for correctness, the API

must be built into the browser and not delievered via an experiment.



.. Should we even document onStartup()?  I think no...