Merge branch 'master' into add-new-activations

tfjs-automl/README.md

@@ -48,10 +48,10 @@ const modelUrl = 'model.json'; // URL to the model.json file.
 const model = await automl.loadImageClassification(modelUrl);
 ```
 
-If you do not want (or cannot) load the model over HTTP you can also load the model separately and directly use the constuctor. 
+If you do not want (or cannot) load the model over HTTP you can also load the model separately and directly use the constructor. 
 This is particularly relevant for __non-browser__ platforms.
 
-The following psuedocode demonstrates this approach:
+The following pseudocode demonstrates this approach:
 
 ```js
 import * as automl from '@tensorflow/tfjs-automl';
@@ -138,10 +138,10 @@ const modelUrl = 'model.json'; // URL to the model.json file.
 const model = await automl.loadObjectDetection(modelUrl);
 ```
 
-If you do not want (or cannot) load the model over HTTP you can also load the model separately and directly use the constuctor. 
+If you do not want (or cannot) load the model over HTTP you can also load the model separately and directly use the constructor. 
 This is particularly relevant for __non-browser__ platforms.
 
-The following psuedocode demonstrates this approach:
+The following pseudocode demonstrates this approach:
 
 ```js
 import * as automl from '@tensorflow/tfjs-automl';

tfjs-automl/src/test_browser.ts

@@ -39,7 +39,7 @@ const testEnv = parseTestEnvFromKarmaFlags(__karma__.config.args, TEST_ENVS);
 if (testEnv != null) {
   setTestEnvs([testEnv]);
 } else {
-  // Run browser tests againts both the webgl backends.
+  // Run browser tests against both the webgl backends.
   setTestEnvs([
     // WebGL.
     {

tfjs-automl/src/test_node.ts

@@ -28,7 +28,7 @@ process.on('unhandledRejection', e => {
   throw e;
 });
 
-// Run node tests againts the cpu backend.
+// Run node tests against the cpu backend.
 setTestEnvs([{name: 'node', backendName: 'cpu'}]);
 
 const runner = new jasmine();

tfjs-backend-wasm/README.md

@@ -47,7 +47,7 @@ tf.setBackend('wasm').then(() => main());
 Starting from Chrome 92 (to be released around July 2021), **cross-origin
 isolation** needs to be set up in your site in order to take advantage of
 the multi-threading support in WASM backend. Without this, the backend
-will fallback to the WASM binary with SIMD-only support (or the vanila version
+will fallback to the WASM binary with SIMD-only support (or the vanilla version
 if SIMD is not enabled). Without multi-threading support, certain models might
 not achieve the best performance.
 

tfjs-tflite/README.md

@@ -88,7 +88,7 @@ enabled by default. In older versions of Chrome, they can be enabled in
 
 Starting from Chrome 92, **cross-origin isolation** needs to be set up in your
 site in order to take advantage of the multi-threading support. Without this, it
-will fallback to the WASM binary with SIMD-only support (or the vanila version
+will fallback to the WASM binary with SIMD-only support (or the vanilla version
 if SIMD is not enabled). Without multi-threading support, certain models might
 not achieve the best performance. See [here][cross origin setup steps] for the
 high-level steps to set up the cross-origin isolation.