Merge pull request #17079 to #17080

Author: magento-engcom-team

app/code/Magento/Catalog/view/adminhtml/web/js/product/weight-handler.js

@@ -67,10 +67,10 @@ define([
         },
 
         /**
-         * Has weight swither
+         * Has weight switcher
          * @returns {*}
          */
-        hasWeightSwither: function () {
+        hasWeightSwitcher: function () {
             return this.$weightSwitcher().is(':visible');
         },
 
@@ -107,7 +107,7 @@ define([
         'Magento_Catalog/js/product/weight-handler': function () {
             this.bindAll();
 
-            if (this.hasWeightSwither()) {
+            if (this.hasWeightSwitcher()) {
                 this.switchWeight();
             }
         },

app/code/Magento/Ui/view/base/web/js/lib/core/element/element.js

@@ -46,7 +46,7 @@ define([
     }
 
     /**
-     * Creates observable propery using 'track' method.
+     * Creates observable property using 'track' method.
      *
      * @param {Object} obj - Object to whom property belongs.
      * @param {String} key - Key of the property.

dev/tests/functional/tests/app/Magento/Widget/Test/Constraint/AssertWidgetCmsPageLink.php

@@ -18,7 +18,7 @@
 class AssertWidgetCmsPageLink extends AbstractConstraint
 {
     /**
-     * Assert that created widget displayed on frontent on Home page and on Advanced Search and
+     * Assert that created widget displayed on frontend on Home page and on Advanced Search and
      * after click on widget link on frontend system redirects you to cms page.
      *
      * @param CmsIndex $cmsIndex

dev/tests/integration/testsuite/Magento/Framework/App/Utility/_files/fixtures/theme/registration.php

@@ -6,4 +6,4 @@
 
 use \Magento\Framework\Component\ComponentRegistrar;
 
-ComponentRegistrar::register(ComponentRegistrar::THEME, 'frontent/Test/theme', __DIR__);
+ComponentRegistrar::register(ComponentRegistrar::THEME, 'frontend/Test/theme', __DIR__);

dev/tests/integration/testsuite/Magento/Framework/App/Utility/_files/patterns/paths_one.txt

@@ -1,2 +1,2 @@
 module Magento_Module *
-theme frontent/Test/theme One*
+theme frontend/Test/theme One*

dev/tests/static/framework/Magento/Sniffs/Less/PropertiesLineBreakSniff.php

@@ -46,7 +46,7 @@ public function process(File $phpcsFile, $stackPtr)
         }
 
         if ($tokens[$prevPtr]['line'] === $tokens[$stackPtr]['line']) {
-            $error = 'Each propery must be on a line by itself';
+            $error = 'Each property must be on a line by itself';
             $phpcsFile->addError($error, $stackPtr, 'SameLine');
         }
     }

lib/web/mage/utils/objects.js

@@ -83,7 +83,7 @@ define([
      * @private
      *
      * @param {Object} parent - Object from which to remove property.
-     * @param {Array} path - Splitted path to the propery.
+     * @param {Array} path - Splitted path to the property.
      */
     function removeNested(parent, path) {
         var field = path.pop();

lib/web/mage/validation/url.js

@@ -42,7 +42,7 @@ define([], function () {
         /**
          * Sanitize url, replacing disallowed chars
          *
-         * @param {Sring} path - url to be normalized
+         * @param {String} path - url to be normalized
          * @returns {String}
          */
         sanitize: function (path) {

setup/performance-toolkit/README.md

@@ -116,7 +116,7 @@ To get more details about available JMeter options, read [Non-GUI Mode](http://j
 For example, you can run the B2C scenario via console with 90 threads for the Frontend Pool and 10 threads for the Admin Pool:
 
     cd {JMeter path}/bin/
-    jmeter -n -t {path to peformance toolkit}/benchmark.jmx -j ./jmeter.log -l ./jmeter-results.jtl -Jhost=magento2.dev -Jbase_path=/ -Jadmin_path=admin -JfrontendPoolUsers=90 -JadminPoolUsers=10
+    jmeter -n -t {path to performance toolkit}/benchmark.jmx -j ./jmeter.log -l ./jmeter-results.jtl -Jhost=magento2.dev -Jbase_path=/ -Jadmin_path=admin -JfrontendPoolUsers=90 -JadminPoolUsers=10
 
 As a result, you will get `jmeter.log` and `jmeter-results.jtl`. The`jmeter.log` contains information about the test run and can be helpful in determining the cause of an error.  The JTL file is a text file containing the results of a test run. It can be opened in the GUI mode to perform analysis of the results (see the *Output* section below).