diff --git a/docs/Contributing/adding-new-UI-components.md b/docs/Contributing/Automatically-generating-UI-component-boilerplate.md
similarity index 52%
rename from docs/Contributing/adding-new-UI-components.md
rename to docs/Contributing/Automatically-generating-UI-component-boilerplate.md
index 27afb46246..80ad32d3b8 100644
--- a/docs/Contributing/adding-new-UI-components.md
+++ b/docs/Contributing/Automatically-generating-UI-component-boilerplate.md
@@ -1,6 +1,9 @@
-# Using `generate` to create boilerplate for a new Fleet UI component
+# Automatically generating UI component boilerplate
 
-## Basic steps to create a new UI component
+Instead of manually creating each file, you can use
+the `generate` utility to automatically create the common boilerplate for a new Fleet UI component.
+
+## Basic steps
 
 1. `cd` into `fleet/frontend/components`
 2. Run `./generate -n NewComponentName`, replacing `NewComponentName` with the desired name for your
@@ -8,7 +11,8 @@
 3. A directory and all boilerplate for the various files of the component will be generated in
    `fleet/frontend/components`
 
-You can also run `./generate -h` for information about the other options available (overwrite and
-specifying destination)
 
-<meta name="pageOrderInSection" value="450">
\ No newline at end of file
+You can also run `./generate -h` for information about the other options available, overwrite and
+specifying destination.
+
+<meta name="pageOrderInSection" value="450">