diff -u b/core/modules/help_topics/help_topics/comment.configuring_content.html.twig b/core/modules/help_topics/help_topics/comment.configuring_content.html.twig
--- b/core/modules/help_topics/help_topics/comment.configuring_content.html.twig
+++ b/core/modules/help_topics/help_topics/comment.configuring_content.html.twig
@@ -15,45 +15,32 @@
 <ol>
   <li>{% trans %}In the <em>Manage</em> administrative menu, navigate to <em>Structure</em> &gt; <a href="{{ comment_types }}"><em>Content types</em></a>.{% endtrans %}</li>
   <li>{% trans %}Select <em>Edit</em> from the dropdown button for the content type where you want to enable commenting.{% endtrans %}</li>
-  <li>Click the <em>Manage fields</em> tab.</li>
-  <li>{% trans %}Locate the <em>Comments</em> field and click
-      <em>Edit</em>. The available options depend on your selection:{% endtrans %}
+  <li>{% trans %}Click the <em>Manage fields</em> tab.{% endtrans %}</li>
+  <li>{% trans %}Locate the <em>Comments</em> field and click <em>Edit</em>. The available options depend on your selection:{% endtrans %}
     <ul>
-      <li>{% trans %}
-          <em>Label</em>: label that will appear before all the comments listed on this particular content type{% endtrans %}
-      </li>
-      <li>{% trans %}<em>Help
-          text</em>: custom instructions that will appear in the comment section of the content type{% endtrans %}</li>
+      <li>{% trans %}<em>Label</em>: label that will appear before all the comments listed on this particular content type{% endtrans %}</li>
+      <li>{% trans %}<em>Help text</em>: custom instructions that will appear in the comment section of the content type{% endtrans %}</li>
       <li>{% trans %}<em>Required field</em>: whether it is required to fill in the comment field{% endtrans %}</li>
-      <li>{% trans %}
-          <em>Threading</em>: whether the comments are displayed in a threaded list (replies are indented to make discussions easier to follow) {% endtrans %}
-      </li>
-      <li>{% trans %}<em>Comments per
-          page</em>: the maximum number of comments displayed on one page (additional pages will be added if you exceed this limit){% endtrans %}
-      </li>
-      <li>{% trans %}<em>Show reply form on the same page as
-          comments</em>: whether the comment reply form is displayed on the same page as the comments. If this is not selected, clicking
-          <em>Reply</em> will take you to a new page where the user can fill in the reply form{% endtrans %}</li>
+      <li>{% trans %}<em>Threading</em>: whether the comments are displayed in a threaded list (replies are indented to make discussions easier to follow) {% endtrans %}</li>
+      <li>{% trans %}<em>Comments per page</em>: the maximum number of comments displayed on one page (additional pages will be added if you exceed this limit){% endtrans %}</li>
+      <li>{% trans %}<em>Show reply form on the same page as comments</em>: whether the comment reply form is displayed on the same page as the comments. If this is not selected, clicking <em>Reply</em> will take you to a new page where the user can fill in the reply form{% endtrans %}</li>
       <li>{% trans %}<em>Preview comments</em>: how previews of comments are being shown{% endtrans %}
         <ul>
           <li>{% trans %}<em>Disabled</em>: the preview is never displayed{% endtrans %}</li>
           <li>{% trans %}<em>Optional</em>: the user can choose whether to display the preview{% endtrans %}</li>
-          <li>{% trans %}<em>Required</em>: the preview is always being shown prior to saving the comment{% endtrans %}
-          </li>
+          <li>{% trans %}<em>Required</em>: the preview is always being shown prior to saving the comment{% endtrans %}</li>
         </ul>
       </li>
       <li>{% trans %}<em>Default value</em>: availability of comments when creating new content.{% endtrans %}
         <ul>
           <li>{% trans %}<em>Open</em>: comments are allowed on any new content of this type{% endtrans %}</li>
-          <li>{% trans %}<em>Closed</em>: no comments are allowed, but any past comments remain visible{% endtrans %}
-          </li>
-          <li>{% trans %}<em>Hidden</em>: no comments are allowed, and past comments are hidden{% endtrans %}
-          </li>
+          <li>{% trans %}<em>Closed</em>: no comments are allowed, but any past comments remain visible{% endtrans %}</li>
+          <li>{% trans %}<em>Hidden</em>: no comments are allowed, and past comments are hidden{% endtrans %}</li>
         </ul>
       </li>
     </ul>
   </li>
-  <li>Click <em>Save setting</em> to save the comment settings for the chose content type.</li>
+  <li>{% trans %}Click <em>Save setting</em> to save the comment settings for the chose content type.{% endtrans %}</li>
 </ol>
 <h2>{% trans %}Additional resources{% endtrans %}</h2>
 <ul>
diff -u b/core/modules/help_topics/help_topics/node.creating_content.html.twig b/core/modules/help_topics/help_topics/node.creating_content.html.twig
--- b/core/modules/help_topics/help_topics/node.creating_content.html.twig
+++ b/core/modules/help_topics/help_topics/node.creating_content.html.twig
@@ -3,14 +3,12 @@
 related:
 - node.overview
 - core.content_structure
-- node.create_content_type
+- node.creating_type
 - field_ui.add_field
 - field_ui.manage_display
 - field_ui.manage_form
 - comment.configuring_content
 - path.overview
-- menu.overview
-- content.revisioning
 ---
 {% set content_types = render_var(url('entity.node_type.collection')) %}
 {% set content_structure = render_var(url('help.help_topic', {'id': 'core.content_structure'})) %}
diff -u b/core/modules/help_topics/help_topics/node.overview.html.twig b/core/modules/help_topics/help_topics/node.overview.html.twig
--- b/core/modules/help_topics/help_topics/node.overview.html.twig
+++ b/core/modules/help_topics/help_topics/node.overview.html.twig
@@ -8,8 +8,6 @@
 <p>{% trans %}A <em>content item</em> is any piece of individual content, such as a page, poll, article, forum topic, or a blog entry.{% endtrans %}</p>
 <h2>{% trans %}What is a content type?{% endtrans %}</h2>
 <p>{% trans %}Content items are divided in <em>content types</em>, which have different purposes and are displayed in very different ways on the site. Examples of content types are page, article, recipe, event, forum topic, and blog entry.{% endtrans %}</p>
-<h2>{% trans %}What is the Node module?{% endtrans %}</h2>
-<p>{% trans %}The Node module manages the creation, editing, deletion, settings, and display of the main site content. Content items managed by the Node module are typically displayed as pages on your site, and include a title, some meta-data (author, creation time, content type, etc.), and optional fields containing text or other data (fields are managed by the Field module).{% endtrans %}</p>
 <h2>{% trans %}Additional resources{% endtrans %}</h2>
 <ul>
   <li><a href="https://www.drupal.org/docs/user_guide/en/planning-structure.html">{% trans %}Drupal User Guide: Planning your content structure{% endtrans %}</a></li>
diff -u b/core/modules/help_topics/help_topics/path.overview.html.twig b/core/modules/help_topics/help_topics/path.overview.html.twig
--- b/core/modules/help_topics/help_topics/path.overview.html.twig
+++ b/core/modules/help_topics/help_topics/path.overview.html.twig
@@ -10,11 +10,9 @@
 <h2>{% trans %}What is a path?{% endtrans %}</h2>
 <p>{% trans %}A path is the unique, last part of the URL for a specific function or piece of content. For example, for a page whose full URL is <em>http://example.com/node/7</em>, the path is <em>node/7</em>. Here are some examples of paths you might find in your site:{% endtrans %}</p>
 <ul>
-  <li>node/7</li>
-  <li>taxonomy/term/6</li>
-  <li>admin/content/comment</li>
-  <li>user/login</li>
-  <li>user/3</li>
+  <li>{% trans %}node/7: Path to a particular content item{% endtrans %}</li>
+  <li>{% trans %}taxonomy/term/6: Path to a taxonomy term page{% endtrans %}</li>
+  <li>{% trans %}user/3: Path to user profile page{% endtrans %}</li>
 </ul>
 <h2>{% trans %}What is an alias?{% endtrans %}</h2>
 <p>{% trans %}The core software has a feature called "URL Alias" that allows you to provide a more understandable name to the content. So, if you have an "About Us" page with the path <em>node/7</em>, you can set up an alias so that your visitors will see it as <em>http://www.example.com/AboutUs</em>. The core Path module, which supports URL aliasing, provides this functionality. The additional module <a href="https://www.drupal.org/projects/pathauto">pathauto</a> automatically generates a URL alias when you create content.{% endtrans %}</p>