diff --git a/src/content/plugins/figma-plugin.md b/src/content/plugins/figma-plugin.md
index f18fc502..1ef6dfe1 100644
--- a/src/content/plugins/figma-plugin.md
+++ b/src/content/plugins/figma-plugin.md
@@ -67,12 +67,18 @@ Invite non-technical teammates like designers or PMs to your Chromatic project a
 
 Every Chromatic plan comes with unlimited collaborators and [fine-grained roles](/docs/collaborators#roles). There are no extra charges "per seat".
 
+
+---
+
+## Frequently asked questions
+
 <details>
 <summary>Want to incorporate Figma in Chromatic?</summary>
 
 Chromatic has [another integration with Figma](/docs/figma-in-chromatic) that brings code and design, side-by-side support into the web app. You’ll be able to view Figma components alongside their linked story right within Chromatic.
 
 </details>
+
 <details>
 <summary>What URLs are supported in the Figma plugin?</summary>
 
@@ -84,3 +90,10 @@ The plugin supports two url formats hosted on Chromatic:
 | Component URL in Chromatic       | `https://www.chromatic.com/component?appId=5ccbc373887ca40020446347&csfId=button&buildNumber=1242&k=64821b99eedbc52679c33cd6-1200-interactive-true&h=7&b=-1` |
 
 </details>
+
+<details>
+<summary>Can I trigger a Chromatic build from Figma?</summary>
+
+No, when you update your Figma project, you must update your code and run a Chromatic build to upgrade the baseline.
+
+</details>
\ No newline at end of file
diff --git a/src/content/plugins/visual-tests-addon.md b/src/content/plugins/visual-tests-addon.md
index 6a5c1bbf..0f3864c1 100644
--- a/src/content/plugins/visual-tests-addon.md
+++ b/src/content/plugins/visual-tests-addon.md
@@ -122,7 +122,7 @@ When you finish accepting changes as baselines in the addon, you're ready to pus
 
 ---
 
-## FAQ
+## Frequently asked questions
 
 <details>
 <summary>What are "local" builds and how are they different from builds?</summary>
diff --git a/src/content/snapshot/branching-and-baselines.md b/src/content/snapshot/branching-and-baselines.md
index 736baad9..22d4080c 100644
--- a/src/content/snapshot/branching-and-baselines.md
+++ b/src/content/snapshot/branching-and-baselines.md
@@ -140,7 +140,7 @@ Use the `--auto-accept-changes` flag with the Chromatic CLI or the `autoAcceptCh
 <details>
   <summary>What if I accidentally accept unwanted changes. Can I delete a build?</summary>
 
-Chromatic does not currently support deleting individual builds within a proejct. Builds are integral to Chromatic's baseline algorithms, making deleting individual links in the chain complex and impossible at the moment.
+Chromatic does not currently support deleting individual builds within a project. Builds are integral to Chromatic's baseline algorithms, making deleting individual links in the chain complex and impossible at the moment.
 
 If you want to revert to a previous baseline, you can use Git to restore old baselines. Identify a past build with the correct baselines, create a new branch for these changes and merge them into the current `main` branch using the `--auto-accept-changes` flag.