diff --git a/core/modules/migrate/migrate.api.php b/core/modules/migrate/migrate.api.php
index 2a2610b..eff51e0 100644
--- a/core/modules/migrate/migrate.api.php
+++ b/core/modules/migrate/migrate.api.php
@@ -22,22 +22,18 @@
  * and the load phase is called "destination".
  *
  * Source, process, and destination phases are each provided by plugins. Source
- * plugins extract data from a data source in "rows". Each row of data is handed
- * off to a series of process plugins, which transform the data if necessary
- * (setting default values, mapping values, etc.). The resulting row is handed
- * off to a destination plugin, which saves the data as some sort of Drupal
- * object (configuration, entity, URL alias, etc.). In setting up a generic
- * migration, the destination may not be completely known; a common example
- * of this is in migrating entities with fields. In this case, there is a
- * load plugin involved, which has the responsibility of loading and setting up
- * the destination.
+ * plugins extract data from a data source in "rows", containing "properties".
+ * Each row is handed off to one or more series of process plugins, where each
+ * series operates to transform the row data into one result property. After all
+ * the properties are processed, the resulting row is handed off to a
+ * destination plugin, which saves the data.
  *
- * The Migrate module provides process plugins for common operations, and
- * destination plugins for Drupal core objects. The Migrate Drupal module
- * provides source plugins to extract data from various versions of Drupal, and
- * load plugins for dealing with various entities and fields. Custom and
- * contributed modules can provide additional plugins; see the
- * @link plugin_api Plugin API topic @endlink for generic information about
+ * The Migrate module provides process plugins for common operations (setting
+ * default values, mapping values, etc.), and destination plugins for Drupal
+ * core objects (configuration, entity, URL alias, etc.). The Migrate Drupal
+ * module provides source plugins to extract data from various versions of
+ * Drupal. Custom and contributed modules can provide additional plugins; see
+ * the @link plugin_api Plugin API topic @endlink for generic information about
  * providing plugins, and sections below for details about the plugin types.
  *
  * The configuration of migrations is stored in configuration entities, which
@@ -46,7 +42,8 @@
  * create a migration manifest; see @ref sec_manifest for details.
  *
  * https://drupal.org/node/2127611 has more complete information on the
- * Migration API.
+ * Migration API, including information on load plugins, which are only used
+ * in Drupal 6 migration.
  *
  * @section sec_source Source plugins
  * Migration source plugins implement
@@ -76,23 +73,16 @@
  * are managed by the
  * \Drupal\migrate\Plugin\MigrateDestinationPluginManager class.
  *
- * @section sec_load Load plugins
- * Migration load plugins implement
- * \Drupal\migrate_drupal\Plugin\MigrateLoadInterface, and generally extend
- * \Drupal\migrate_drupal\Plugin\migrate\load\LoadEntity. Their only annotation
- * is a generic PluginID annotation, and they must be in namespace subdirectory
- * Plugin\migrate\load under the namespace that defines them. Migration load
- * plugins are managed by the \Drupal\migrate\Plugin\MigratePluginManager class.
- *
  * @section sec_entity Migration configuration entities
  * The definition of how to migrate each type of data is stored in configuration
  * entities. The migration configuration entity class is
  * \Drupal\migrate\Entity\Migration, with interface
  * \Drupal\migrate\Entity\MigrationEntity; the configuration schema can be found
  * in the migrate.schema.yml file. Migration configuration consists of IDs and
- * configuration for the source, process, load (if needed), and destination
- * plugins, as well as information on dependencies. You can find examples of
- * migration configuration files in the
+ * configuration for the source, process, and destination plugins, as well as
+ * information on dependencies. Process configuration consists of sections, each
+ * of which defines the series of process plugins needed for one destination
+ * property. You can find examples of migration configuration files in the
  * core/modules/migrate_drupal/config/install directory.
  *
  * @section sec_manifest Migration manifests