diff --git a/core/modules/migrate/migrate.api.php b/core/modules/migrate/migrate.api.php
index 5c08107..53c48af 100644
--- a/core/modules/migrate/migrate.api.php
+++ b/core/modules/migrate/migrate.api.php
@@ -24,15 +24,15 @@
  * the term 'load' refers to loading data from storage.
  *
  * In the source phase, a set of data, called the row, is retrieved from the
- * data source. The data source is typically a database, but it can also be
- * for example, files (e.g., CSV, JSON or XML) or web services (e.g.,
- * RSS or REST). The row is sent to the process phase where it is transformed
- * as needed or marked to be skipped. Processing can also determine if a 'stub'
- * needs to be created. For example, if a term has a parent term that does not
- * exist yet, a stub term is created so that the parent relation can be
- * established, and the stub is updated at a later point. After processing, the
- * transformed row is passed to the destination phase where it is loaded
- * (saved) into the target Drupal site.
+ * data source. The data source is typically a database, but it can also be,
+ * for example, files (CSV, JSON or XML) or web services (RSS or REST). The row
+ * is sent to the process phase where it is transformed as needed or marked to
+ * be skipped. Processing can also determine if a 'stub' needs to be created.
+ * For example, if a term has a parent term that does not exist yet, a stub
+ * term is created so that the parent relation can be established, and the stub
+ * is updated at a later point. After processing, the transformed row is passed
+ * to the destination phase where it is loaded (saved) into the target Drupal
+ * site.
  *
  * The overall ETL process and the three phases (source, process and
  * destination) are all defined as migration plugins.