diff --git a/core/modules/content_translation/content_translation.admin.inc b/core/modules/content_translation/content_translation.admin.inc
index 5bd5dcf..b65eeea 100644
--- a/core/modules/content_translation/content_translation.admin.inc
+++ b/core/modules/content_translation/content_translation.admin.inc
@@ -340,7 +340,4 @@ function content_translation_form_language_content_settings_submit(array $form,
   \Drupal::entityManager()->clearCachedDefinitions();
   \Drupal::service('router.builder_indicator')->setRebuildNeeded();
   \Drupal::service('content_translation.updates_manager')->updateDefinitions($entity_types);
-
-  drupal_set_message(t('Settings successfully updated.'));
 }
-
diff --git a/core/modules/content_translation/content_translation.module b/core/modules/content_translation/content_translation.module
index d9e0b18..4277ea0 100644
--- a/core/modules/content_translation/content_translation.module
+++ b/core/modules/content_translation/content_translation.module
@@ -75,8 +75,9 @@ function content_translation_language_types_info_alter(array &$language_types) {
  * Implements hook_entity_type_alter().
  *
  * The content translation UI relies on the entity info to provide its features.
- * See the documentation of hook_entity_type_build() in the Entity API documentation
- * for more details on all the entity info keys that may be defined.
+ * See the documentation of hook_entity_type_build() in the Entity API
+ * documentation for more details on all the entity info keys that may be
+ * defined.
  *
  * To make Content Translation automatically support an entity type some keys
  * may need to be defined, but none of them is required unless the entity path
@@ -84,11 +85,11 @@ function content_translation_language_types_info_alter(array &$language_types) {
  * "/taxonomy/term/{taxonomy_term}"), in which case at least the 'canonical' key
  * in the 'links' entity info property must be defined.
  *
- * Every entity type needs a translation handler to be translated. This can
- * be specified through the 'translation' key in the 'handlers' entity
- * annotation property. If an entity type is translatable and no translation
- * handler is defined, \Drupal\content_translation\ContentTranslationHandler
- * will be assumed. Every translation handler must implement
+ * Every entity type needs a translation handler to be translated. This can be
+ * specified through the 'translation' key in the 'handlers' entity annotation
+ * property. If an entity type is translatable and no translation handler is
+ * defined, \Drupal\content_translation\ContentTranslationHandler will be
+ * assumed. Every translation handler must implement
  * \Drupal\content_translation\ContentTranslationHandlerInterface.
  *
  * To implement its business logic the content translation UI relies on various
@@ -102,9 +103,9 @@ function content_translation_language_types_info_alter(array &$language_types) {
  * \Drupal\content_translation\ContentTranslationMetadataWrapperInterface.
  *
  * If the entity paths match the default pattern above and there is no need for
- * an entity-specific translation handler, Content Translation will
- * provide built-in support for the entity. However enabling translation for
- * each translatable bundle will be required.
+ * an entity-specific translation handler, Content Translation will provide
+ * built-in support for the entity. However enabling translation for each
+ * translatable bundle will be required.
  *
  * @see \Drupal\Core\Entity\Annotation\EntityType
  */