diff --git a/core/lib/Drupal/Core/Config/Entity/ConfigDependencyManager.php b/core/lib/Drupal/Core/Config/Entity/ConfigDependencyManager.php
index 14eac1d..84a0462 100644
--- a/core/lib/Drupal/Core/Config/Entity/ConfigDependencyManager.php
+++ b/core/lib/Drupal/Core/Config/Entity/ConfigDependencyManager.php
@@ -15,17 +15,17 @@
  *
  * Configuration entities can depend on modules, themes and other configuration
  * entities. The dependency system is used during configuration installation,
- * uninstallation and synchronization to ensure that configuration entities are
+ * uninstallation, and synchronization to ensure that configuration entities are
  * handled in the correct order. For example, node types are created before
  * their fields, and both are created before the view display configuration.
  *
  * If a configuration entity is provided as default configuration by an
- * extension (modules, themes, or profiles), the extension has to depend on any
+ * extension (module, theme, or profile), the extension has to depend on any
  * modules or themes that the configuration depends on. For example, if a view
  * configuration entity is provided by an installation profile and the view will
  * not work without a certain module, the profile must declare a dependency on
  * this module in its info.yml file. If you do not want your extension to always
- * depend on a particular module that one of the default configuration entities
+ * depend on a particular module that one of its default configuration entities
  * depends on, you can use a sub-module: move the configuration entity to the
  * sub-module instead of including it in the main extension, and declare the
  * module dependency in the sub-module only.
@@ -35,12 +35,12 @@
  * \Drupal\Core\Plugin\PluginDependencyTrait to manage dependencies. The class
  * must implement
  * \Drupal\Core\Config\Entity\ConfigEntityInterface::calculateDependencies(),
- * which should calculate (and return) the dependencies. Use
+ * which should calculate (and return) the dependencies. In this method, use
  * \Drupal\Core\Config\Entity\ConfigEntityBase::addDependency() to add
  * dependencies. Most implementations call
  * \Drupal\Core\Config\Entity\ConfigEntityBase::calculateDependencies() since it
  * provides a generic implementation that will discover dependencies due to
- * plugins and third party settings. To get a configuration entities current
+ * plugins and third party settings. To get a configuration entity's current
  * dependencies without forcing a recalculation use
  * \Drupal\Core\Config\Entity\ConfigEntityInterface::getDependencies().
  *
diff --git a/core/lib/Drupal/Core/Config/Entity/ConfigEntityBase.php b/core/lib/Drupal/Core/Config/Entity/ConfigEntityBase.php
index ea1c570..96e877b 100644
--- a/core/lib/Drupal/Core/Config/Entity/ConfigEntityBase.php
+++ b/core/lib/Drupal/Core/Config/Entity/ConfigEntityBase.php
@@ -367,8 +367,8 @@ public function link($text = NULL, $rel = 'edit-form', array $options = []) {
   /**
    * Overrides \Drupal\Core\Entity\DependencyTrait:addDependency().
    *
-   * Note that this function should only be called from implementation of
-   * \Drupal\Core\Config\Entity\ConfigEntityInterface::calculateDependencies()
+   * Note that this function should only be called from implementations of
+   * \Drupal\Core\Config\Entity\ConfigEntityInterface::calculateDependencies(),
    * as dependencies are recalculated during every entity save.
    *
    * @see \Drupal\Core\Config\Entity\ConfigEntityDependency::hasDependency()