Fern Editor: Update

Author: fern-api[bot]

fern/products/docs/pages/getting-started/how-it-works.mdx

@@ -7,6 +7,8 @@ Fern combines your API specifications, static Markdown files (like how-to guides
 
 This process is built around two major workflows: **editing** and **deploying** your documentation.
 
+EDITS FROM STAGING!
+
 <Accordion title="System architecture">
 
 This diagram shows the technical infrastructure that powers the documentation generation process.
@@ -77,8 +79,8 @@ flowchart TD
 
 You can update your documentation in two ways:
 
-- **Direct editing**: Open a pull request directly in the [GitHub repository that contains your docs](/learn/docs/getting-started/project-structure) (including your `docs.yml` configuration and Markdown files). 
-- **Fern Editor**: Use the [Fern Editor](/learn/docs/writing-content/fern-editor) to modify your docs without touching code. The Fern GitHub App fetches the current state from your docs repository and passes it to the Fern Editor. When you submit changes, the Fern GitHub App automatically opens a pull request for review. 
+- **Direct editing**: Open a pull request directly in the [GitHub repository that contains your docs](/learn/docs/getting-started/project-structure) (including your `docs.yml` configuration and Markdown files).
+- **Fern Editor**: Use the [Fern Editor](/learn/docs/writing-content/fern-editor) to modify your docs without touching code. The Fern GitHub App fetches the current state from your docs repository and passes it to the Fern Editor. When you submit changes, the Fern GitHub App automatically opens a pull request for review.
 
 After the update goes through your review process, an approver can merge it.