diff --git a/qawolf/getting-the-most-out-of-mapping.mdx b/qawolf/getting-the-most-out-of-mapping.mdx
index a5bb7ff..7cbfe15 100644
--- a/qawolf/getting-the-most-out-of-mapping.mdx
+++ b/qawolf/getting-the-most-out-of-mapping.mdx
@@ -52,7 +52,7 @@ You don't have to rely entirely on Mapping to find flows on its own. You can cli
 - Specific flows you want to make sure are captured
 - Verifying that Mapping understood a flow correctly
 
-To use this: stop the AI, click through the flow yourself, and look for the **Add flows** button that appears.
+To use this: stop the AI, click through the flow yourself, and look for the **Save as flows** button that appears.
 
 ## Use Automate for flows that need more control
 
@@ -60,4 +60,4 @@ Mapping is designed for breadth — getting a full outline of an app's testable
 
 <Tip>
   A common pattern: run Mapping to generate a broad outline, then use Automate to build out the flows that need more precision.
-</Tip>
\ No newline at end of file
+</Tip>