ENGCOM-5108: Grammatical mistake in the comments #22858

Author: sivaschenko

lib/internal/Magento/Framework/Setup/Declaration/Schema/Db/StatementAggregator.php

@@ -36,7 +36,7 @@ private function canDoMerge(Statement $bankStatement, Statement $statement)
         }
 
         /**
-         * If we add trigger after some specific statement, than we say that statement is final
+         * If we add trigger after some specific statement, then we say that statement is final
          * and can`t be updated anymore. Otherwise trigger can fail.
          *
          * Example: while migrating data from one column to another and another column should be removed,

lib/internal/Magento/Framework/Setup/Declaration/Schema/Dto/Columns/ColumnNullableAwareInterface.php

@@ -7,7 +7,7 @@
 
 /**
  * Provides nullable flag for element.
- * If column element implement this interface, than it will have NULL or NOT NULL flag in column definition.
+ * If column element implement this interface, then it will have NULL or NOT NULL flag in column definition.
  */
 interface ColumnNullableAwareInterface
 {

lib/internal/Magento/Framework/Setup/Declaration/Schema/Dto/Columns/ColumnUnsignedAwareInterface.php

@@ -7,7 +7,7 @@
 
 /**
  * Unsigned flag provider for element.
- * If column element implement this interface, than it will have UNSIGNED flag in column
+ * If column element implement this interface, then it will have UNSIGNED flag in column
  * definition.
  */
 interface ColumnUnsignedAwareInterface

lib/internal/Magento/Framework/Setup/Declaration/Schema/Operations/AddColumn.php

@@ -164,7 +164,7 @@ private function setupTriggersIfExists(Statement $statement, ElementHistory $ele
         }
         $statements = [$statement];
         /**
-         * If column has triggers, only than we need to create temporary index on it.
+         * If column has triggers, only then we need to create temporary index on it.
          * As triggers means, that we will not enable primary key until all data will be transferred,
          * so column can left without key (as primary key is disabled) and this cause an error.
          */

lib/internal/Magento/Framework/Setup/Patch/PatchInterface.php

@@ -19,7 +19,7 @@ public function getAliases();
 
     /**
      * Run code inside patch
-     * If code fails, patch must be reverted, in case when we are speaking about schema - than under revert
+     * If code fails, patch must be reverted, in case when we are speaking about schema - then under revert
      * means run PatchInterface::revert()
      *
      * If we speak about data, under revert means: $transaction->rollback()

lib/internal/Magento/Framework/Setup/Patch/PatchRegistry.php

@@ -68,7 +68,7 @@ public function __construct(PatchFactory $patchFactory, PatchHistory $patchHisto
     /**
      * Register all dependents to patch
      *
-     * @param string | DependentPatchInterface $patchName
+     * @param string|DependentPatchInterface $patchName
      */
     private function registerDependents(string $patchName)
     {
@@ -130,6 +130,8 @@ private function getDependentPatches(string $patch)
     }
 
     /**
+     * Get patch dependencies.
+     *
      * @param string $patch
      * @return string[]
      */
@@ -146,7 +148,7 @@ private function getDependencies(string $patch)
 
             $depInstance = $this->registerPatch($dep);
             /**
-             * If a patch already have applied dependency - than we definently know
+             * If a patch already have applied dependency - then we definitely know
              * that all other dependencies in dependency chain are applied too, so we can skip this dep
              */
             if (!$depInstance) {
@@ -189,7 +191,7 @@ public function getReverseIterator()
     /**
      * Retrieve iterator of all patch instances
      *
-     * If patch have dependencies, than first of all dependencies should be installed and only then desired patch
+     * If patch have dependencies, then first of all dependencies should be installed and only then desired patch
      *
      * @return \ArrayIterator
      */

lib/internal/Magento/Framework/Setup/Patch/PatchVersionInterface.php

@@ -14,11 +14,10 @@ interface PatchVersionInterface
 {
     /**
      * This version associate patch with Magento setup version.
-     * For example, if Magento current setup version is 2.0.3 and patch version is 2.0.2 than
+     * For example, if Magento current setup version is 2.0.3 and patch version is 2.0.2 then
      * this patch will be added to registry, but will not be applied, because it is already applied
      * by old mechanism of UpgradeData.php script
      *
-     *
      * @return string
      * @deprecated since appearance, required for backward compatibility
      */