diff --git a/editor/index.mdx b/editor/index.mdx
index a39ea4d7e..3b14a32de 100644
--- a/editor/index.mdx
+++ b/editor/index.mdx
@@ -11,7 +11,7 @@ keywords: ["editor", "visual", "collaborative", "web editor"]
 
 ## Open the editor
 
-Open the editor from the [Editor](https://app.mintlify.com/editor) tab in your Mintlify dashboard. Any member of your organization can open the editor; what you can do inside depends on your [role](/dashboard/roles). Admins and editors can edit and publish, and viewers can browse content and leave [comments](/editor/comments) or [suggestions](/editor/suggestions).
+Open the editor from the [Editor](https://app.mintlify.com/editor) tab in your Mintlify dashboard. Any member of your organization can open the editor, but what you can do inside depends on your [role](/dashboard/roles). Admins and editors can edit and publish, and viewers can browse content and leave [comments](/editor/comments) or [suggestions](/editor/suggestions).
 
 ## How the editor works
 
diff --git a/editor/settings.mdx b/editor/settings.mdx
index 9f3e123d1..317ffadcc 100644
--- a/editor/settings.mdx
+++ b/editor/settings.mdx
@@ -114,7 +114,7 @@ The **Danger zone** section of the editor settings panel contains actions that c
 **Reset editor** forces the editor to discard its local state and sync with your Git repository. If the editor gets stuck out of sync with your repo, reset the editor. For example, if the file tree is empty or shows errors like `Unable to find docs.json` even though the file exists on your deployment branch and your live site builds normally.
 
 <Warning>
-  If you reset the editor, you discard any unpublished changes that haven't been committed to Git. If you have pending edits you want to keep, publish them first.
+  If you reset the editor, you discard any unpublished changes that you haven't committed to Git. If you have pending edits you want to keep, publish them first.
 </Warning>
 
 To reset the editor:
diff --git a/editor/suggestions.mdx b/editor/suggestions.mdx
index 87b2ac968..54727b02b 100644
--- a/editor/suggestions.mdx
+++ b/editor/suggestions.mdx
@@ -7,9 +7,9 @@ keywords: ["suggestions", "suggesting", "collaboration", "review"]
 
 Suggestions let you propose changes to text while preserving the current content. Teammates can review, accept, or reject your suggestions.
 
-Suggesting mode applies to page text. Editors and admins can accept or reject any suggestion; viewers cannot. See [roles](/dashboard/roles) for details.
+Suggesting mode applies to page text. Editors and admins can accept or reject any suggestion, but viewers cannot. See [roles](/dashboard/roles) for details.
 
-Pending suggestions appear as highlighted text in the editor and are listed in the sidebar alongside comments so reviewers can find them.
+Pending suggestions appear as highlighted text in the editor. The sidebar lists them alongside comments so reviewers can find them.
 
 ## Make suggestions
 
diff --git a/editor/tutorial.mdx b/editor/tutorial.mdx
index 6c15807d4..96faab5be 100644
--- a/editor/tutorial.mdx
+++ b/editor/tutorial.mdx
@@ -51,7 +51,7 @@ This tutorial walks you through a complete content update using the editor. You'
       You can also click **Save in branch** to commit your changes without opening a pull request yet. This is useful if you want to keep editing before requesting review.
     </Note>
 
-    After the pull request is created, a preview deployment builds automatically. The publish menu shows the preview URL, a temporary link where your changes render exactly as they would on your live site. Share this URL with your reviewers.
+    After you create the pull request, a preview deployment builds automatically. The publish menu shows the preview URL, a temporary link where your changes render exactly as they would on your live site. Share this URL with your reviewers.
   </Step>
   <Step title="Get your pull request approved">
     Share the pull request with your team. Reviewers can open the pull request in GitHub or GitLab to leave comments, request changes, or approve it.