fix typos in several files

History.md

@@ -394,7 +394,7 @@ N/A
   4.2.1 to 4.2.5.
   [PR #11020](https://github.com/meteor/meteor/pull/11020)
 
-* The `url` package now provides an isomorphic implentation of the [WHATWG `url()`
+* The `url` package now provides an isomorphic implementation of the [WHATWG `url()`
   API](https://url.spec.whatwg.org/).
   While remaining backwards compatible, you can now also import `URL` and `URLSearchParams` from `meteor/url`.
   These will work for both modern and legacy browsers as well as node.
@@ -3253,7 +3253,7 @@ N/A
   fibers unless the `METEOR_DISABLE_FS_FIBERS` environment variable is
   explicitly set to a falsy value. For larger apps, this change results in
   significant build performance improvements due to the creation of fewer
-  fibers and the avoidance of unnecessary asyncronous delays.
+  fibers and the avoidance of unnecessary asynchronous delays.
   https://github.com/meteor/meteor/pull/7975/commits/ca4baed90ae0675e55c93976411d4ed91f12dd63
 
 * Running Meteor as `root` is still discouraged, and results in a fatal
@@ -3660,7 +3660,7 @@ N/A
 * `App.appendToConfig` allows adding custom tags to config.xml.
   [#7307](https://github.com/meteor/meteor/pull/7307)
 
-* When using `ROOT_URL` with a path, relative CSS URLs are rewriten
+* When using `ROOT_URL` with a path, relative CSS URLs are rewritten
   accordingly. [#5837](https://github.com/meteor/meteor/issues/5837)
 
 * Fixed bugs:
@@ -3779,7 +3779,7 @@ N/A
 
 * Adds `defineMutationMethods` option (default: true) to `new Mongo.Collection` to override default behavior that sets up mutation methods (/collection/[insert|update...]) [PR #5778](https://github.com/meteor/meteor/pull/5778)
 
-* Allow overridding the default warehouse url by specifying `METEOR_WAREHOUSE_URLBASE` [PR #7054](https://github.com/meteor/meteor/pull/7054)
+* Allow overriding the default warehouse url by specifying `METEOR_WAREHOUSE_URLBASE` [PR #7054](https://github.com/meteor/meteor/pull/7054)
 
 * Allow `_id` in `$setOnInsert` in Minimongo: https://github.com/meteor/meteor/pull/7066
 
@@ -3796,7 +3796,7 @@ N/A
 * PhantomJS is no longer included in the Meteor dev bundle (#6905). If you
   previously relied on PhantomJS for local testing, the `spiderable`
   package, Velocity tests, or testing Meteor from a checkout, you should
-  now install PhantomJS yourself, by running the following commmand:
+  now install PhantomJS yourself, by running the following command:
   `meteor npm install -g phantomjs-prebuilt`
 
 * The `babel-compiler` package now looks for `.babelrc` files and
@@ -4298,7 +4298,7 @@ a shorter list of breaking changes you should be aware of when upgrading.
 * `meteor-platform` has been deprecated in favor of the smaller `meteor-base`,
   with apps listing their other dependencies explicitly.  The v1.2 upgrader
   will rewrite `meteor-platform` in existing apps.  `meteor-base` puts fewer
-  symbols in the global namepsace, so it's no longer true that all apps
+  symbols in the global namespace, so it's no longer true that all apps
   have symbols like `Random` and `EJSON` in the global namespace.
 
 * New packages: `ecmascript`, `es5-shim`, `ecmascript-collections`, `promise`,
@@ -5544,7 +5544,7 @@ will not be able to use versions of packages that use the new features.
 
 ### Other Changes
 
-* Offically support `Meteor.wrapAsync` (renamed from
+* Officially support `Meteor.wrapAsync` (renamed from
   `Meteor._wrapAsync`). Additionally, `Meteor.wrapAsync` now lets you
   pass an object to bind as `this` in the wrapped call. See
   https://docs.meteor.com/#meteor_wrapasync.
@@ -7826,7 +7826,7 @@ tmeasday, and workmad3.
 * On the client, `Meteor.apply` takes a new `wait` option, which ensures that no
   further method calls are sent to the server until this method is finished; it
   is used for login and logout methods in order to keep the user ID
-  well-defined. You can also specifiy an `onReconnect` handler which is run when
+  well-defined. You can also specify an `onReconnect` handler which is run when
   re-establishing a connection; Meteor Accounts uses this to log back in on
   reconnect.
 

Roadmap.md

@@ -67,7 +67,7 @@ Meteor free deploy is back.
 - Status: shipped in January 2021
 - PRs: https://github.com/meteor/meteor/pull/11117
 
-HMR is avaible since Meteor 2.0
+HMR is available since Meteor 2.0
 
 ### Vue.js
 - Leaders: [Brian Mulhall](https://github.com/BrianMulhall)

packages/accounts-base/accounts_server.js

@@ -107,7 +107,7 @@ export class AccountsServer extends AccountsCommon {
   // @override of "abstract" non-implementation in accounts_common.js
   userId() {
     // This function only works if called inside a method or a pubication.
-    // Using any of the infomation from Meteor.user() in a method or
+    // Using any of the information from Meteor.user() in a method or
     // publish function will always use the value from when the function first
     // runs. This is likely not what the user expects. The way to make this work
     // in a method or publish function is to do Meteor.find(this.userId).observe
@@ -348,7 +348,7 @@ export class AccountsServer extends AccountsCommon {
     if (!result)
       throw new Error("result is required");
 
-    // XXX A programming error in a login handler can lead to this occuring, and
+    // XXX A programming error in a login handler can lead to this occurring, and
     // then we don't call onLogin or onLoginFailure callbacks. Should
     // tryLoginMethod catch this case and turn it into an error?
     if (!result.userId && !result.error)
@@ -721,7 +721,7 @@ export class AccountsServer extends AccountsCommon {
     this._server.publish("meteor.loginServiceConfiguration", () => {
       const { ServiceConfiguration } = Package['service-configuration'];
       return ServiceConfiguration.configurations.find({}, {fields: {secret: 0}});
-    }, {is_auto: true}); // not techincally autopublish, but stops the warning.
+    }, {is_auto: true}); // not technically autopublish, but stops the warning.
 
     // Use Meteor.startup to give other packages a chance to call
     // setDefaultPublishFields.

packages/accounts-password/password_server.js

@@ -222,7 +222,7 @@ const generateCasePermutationsForString = string => {
     permutations = [].concat(...(permutations.map(prefix => {
       const lowerCaseChar = ch.toLowerCase();
       const upperCaseChar = ch.toUpperCase();
-      // Don't add unneccesary permutations when ch is not a letter
+      // Don't add unnecessary permutations when ch is not a letter
       if (lowerCaseChar === upperCaseChar) {
         return [prefix + ch];
       } else {

packages/accounts-password/password_tests.js

@@ -877,7 +877,7 @@ if (Meteor.isClient) (() => {
     logoutStep,
     function (test, expect) {
       // Test that Meteor.logoutOtherClients logs out a second
-      // authentcated connection while leaving Accounts.connection
+      // authenticated connection while leaving Accounts.connection
       // logged in.
       const secondConn = DDP.connect(Meteor.absoluteUrl());
       let token;

packages/babel-compiler/README.md

@@ -21,7 +21,7 @@ Meteor's Babel support consists of the following core packages:
 The `babel-compiler` package exports the `Babel` symbol, which exposes
 functionality provided by the
 [`meteor-babel`](https://www.npmjs.com/package/meteor-babel) NPM package,
-which is in turn implmented using the
+which is in turn implemented using the
 [`babel-core`](https://www.npmjs.com/package/babel-core) NPM package.
 Note that you can only use the `babel-compiler` package on the server.
 

packages/ddp/DDP.md

@@ -26,7 +26,7 @@ minor revisions of DDP might add extra fields without changing the DDP version;
 the client must therefore silently ignore unknown fields.  However, the client
 must not send extra fields other than those documented in the DDP protocol, in
 case these extra fields have meaning to future servers.  On the server, all
-field changes must be optional/ignorable for compatability with older clients;
+field changes must be optional/ignorable for compatibility with older clients;
 otherwise a new protocol version would be required.
 
 ## Establishing a DDP Connection:

packages/es5-shim/README.md

@@ -2,7 +2,7 @@
 [Source code of released version](https://github.com/meteor/meteor/tree/master/packages/es5-shim) | [Source code of development version](https://github.com/meteor/meteor/tree/devel/packages/es5-shim)
 ***
 
-This package improves ECMAScript 5 compliance in all browers, particularly older browsers, and especially Internet Explorer 8 (and earlier).
+This package improves ECMAScript 5 compliance in all browsers, particularly older browsers, and especially Internet Explorer 8 (and earlier).
 
 Like the `ecmascript` package, `es5-shim` is [installed by default](https://github.com/meteor/meteor/blob/22bd755918/tools/static-assets/skel/.meteor/packages#L11) for all new apps. Though it technically can be removed, the expectation is that it will only be removed if the app author wishes to install an equivalent package instead (e.g. something based on [`core-js`](https://github.com/zloirock/core-js)), or wishes to drop support for older browsers altogether.
 

packages/logic-solver/README.md

@@ -1050,7 +1050,7 @@ time-consuming operation.
 
 Finds a Solution that minimizes the value of
 `Logic.weightedSum(formulas, weights)`, and adds a requirement that
-this mininum value is obtained (in the sense of calling
+this minimum value is obtained (in the sense of calling
 `Solver#require` on this Solver).
 
 To determine this minimum value, call

packages/minifier-css/minifier.js

@@ -14,7 +14,7 @@ const CssTools = {
    */
   parseCss(cssText, options = {}) {
     // This function previously used the `css-parse` npm package, which
-    // set the name of the css file being pased using  { source: 'filename' }.
+    // set the name of the css file being parsed using  { source: 'filename' }.
     // If included, we'll convert this to the `postcss` equivalent, to maintain
     // backwards compatibility.
     if (options.source) {

packages/rate-limit/README.md

@@ -46,7 +46,7 @@ called a certain method and restrict them to a certain number of calls per
 user defined time frame. So we generate a unique string key (to be used as
 keys in a counters object) to represent each specific methodName + user
 combination. Since this rule applies to multiple user, we need to concatenate
-the differnet input key names with their values. For example, if we had a rule
+the different input key names with their values. For example, if we had a rule
 with matchers as such:
 
 ```javascript
@@ -71,4 +71,4 @@ every time the intervalTime is passed, at which point we delete the current
 dictionary of counters we store. Every time a rule matches to an input, we
 determine the unique key string and check if it's counters have exceeded the
 allowed amounts, returning an error to the user letting them know that a rate
-limit has been reached.
+limit has been reached.

packages/url/legacy.js

@@ -10,5 +10,5 @@ try {
   ].join("\n"));
 }
 
-// backwards compatability
+// backwards compatibility
 require('./modern.js');

packages/url/modern.js

@@ -4,5 +4,5 @@ URLSearchParams = global.URLSearchParams;
 exports.URL = URL;
 exports.URLSearchParams = URLSearchParams;
 
-// backwards compatability
+// backwards compatibility
 Object.assign(URL, require('./bc/url_client'));

packages/url/server.js

@@ -21,5 +21,5 @@ setMinimumBrowserVersions({
   electron: [0, 20],
 }, module.id);
 
-// backwards compatability
-Object.assign(exports.URL, require('./bc/url_server'));
+// backwards compatibility
+Object.assign(exports.URL, require('./bc/url_server'));

packages/url/tests/main.js

@@ -5,5 +5,5 @@ Tinytest.add("url - sanity", function (test) {
   test.equal(typeof URLSearchParams, "function");
 });
 
-// backwards compatability
+// backwards compatibility
 require('../bc/url_tests');

packages/webapp/connect.js

@@ -5,7 +5,7 @@ export function connect(...connectArgs) {
   const originalUse = handlers.use;
 
   // Wrap the handlers.use method so that any provided handler functions
-  // alway run in a Fiber.
+  // always run in a Fiber.
   handlers.use = function use(...useArgs) {
     const { stack } = this;
     const originalLength = stack.length;
@@ -21,7 +21,7 @@ export function connect(...connectArgs) {
       if (originalHandle.length >= 4) {
         // If the original handle had four (or more) parameters, the
         // wrapper must also have four parameters, since connect uses
-        // handle.length to dermine whether to pass the error as the first
+        // handle.length to determine whether to pass the error as the first
         // argument to the handle function.
         entry.handle = function handle(err, req, res, next) {
           return Promise.asyncApply(originalHandle, this, arguments);

packages/webapp/webapp_tests.js

@@ -157,7 +157,7 @@ Tinytest.addAsync(
     };
 
     // It's okay to set this global state because we're not going to yield
-    // before settng it back to what it was originally.
+    // before setting it back to what it was originally.
     WebAppInternals.setInlineScriptsAllowed(true);
 
     {

scripts/doctool.md

@@ -26,7 +26,7 @@ Examples:
  *
 For lines that don't, no big deal.
 
-    Leading whitspace will be preserved here.
+    Leading whitespace will be preserved here.
 
  * We can create a bullet list in here:
  *
@@ -54,4 +54,4 @@ no stripping of `*` characters on any line.
 /// Multiple consecutive lines that start with `///` are
 /// treated together as a single doc comment.
 /** Separate doc comments get separate paragraphs. */
-```
+```

tools/README.md

@@ -126,7 +126,7 @@ variable `SELF_TEST_TOOL_NODE_FLAGS` could be used the same way
 `TOOL_NODE_FLAGS` is used. If you are setting the env variable
 `SELF_TEST_TOOL_NODE_FLAGS` with `TOOL_NODE_FLAGS`, consider specifying a
 custom port, as they could collide trying to listen to the same port.
-To set a custom port, you could set the variable in the followind manner
+To set a custom port, you could set the variable in the following manner
 `SELF_TEST_TOOL_NODE_FLAGS="--debug-brk=5859"` and the debugger will
 listen to the port 5859 and not the default 5858.