diff --git a/core-blocks/subhead/index.js b/core-blocks/subhead/index.js
index f170d7fc95d15..f5e56c47071c5 100644
--- a/core-blocks/subhead/index.js
+++ b/core-blocks/subhead/index.js
@@ -19,7 +19,7 @@ import './style.scss';
 export const name = 'core/subhead';
 
 export const settings = {
-	title: __( 'Subhead' ),
+	title: __( 'Subheading' ),
 
 	description: __( 'What\'s a subhead? Smaller than a headline, bigger than basic text.' ),
 
@@ -88,7 +88,7 @@ export const settings = {
 					} }
 					style={ { textAlign: align } }
 					className={ className }
-					placeholder={ placeholder || __( 'Write subhead…' ) }
+					placeholder={ placeholder || __( 'Write subheading…' ) }
 				/>
 			</Fragment>
 		);
diff --git a/docs/reference/faq.md b/docs/reference/faq.md
index 88d181f954c88..6fdf499268d18 100644
--- a/docs/reference/faq.md
+++ b/docs/reference/faq.md
@@ -30,7 +30,7 @@ The current WordPress editor is an open text window—it’s always been a wonde
 - Pasted links for embeds.
 - `Shortcodes` for specialized assets from plugins.
 - Featured images for the image at the top of a post or page.
-- Excerpts for subheads.
+- Excerpts for subheadings.
 - Widgets for content on the side of a page.
 
 As we thought about these uses and how to make them obvious and consistent, we began to embrace the concept of “blocks.” All of the above items could be blocks: easy to search and understand, and easy to dynamically shift around the page. The block concept is very powerful, and if designed thoughtfully, can offer an outstanding editing and publishing experience.