You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: editor.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Here is how you'll typically work in the visual editor:
29
29
30
30
<Steps>
31
31
<Steptitle="Choose your branch">
32
-
Create a branch or make changes directly to your deployment branch. We recommend creating a branch so that you can preview your changes before they go live. Learn more about [working with branches](/guides/branches).
32
+
Create a branch or make changes directly to your deployment branch. We recommend creating a branch so that you can preview your changes before they go live.
33
33
</Step>
34
34
<Steptitle="Open your file">
35
35
Navigate to an existing file in the sidebar or create a new one using the file explorer.
@@ -179,7 +179,7 @@ Edit your `docs.json` file to add new pages and remove deleted pages from your s
179
179
180
180
**Example: Add a Themes page to the Profile group**
181
181
182
-
Imagine you wrote a new page titled Themes and you want to add it to the Profile group in your documentation. Add the path to the new page to the `pages` array of the `Profile` group in your `docs.json` file like in the following example.
182
+
In this example, you created a new page titled Themes and you want to add it to the Profile group in your documentation. Add the path to the new page to the `pages` array of the `Profile` group in your `docs.json` file for it to appear in your site navigation.
183
183
184
184
```json title="Adding a Themes page to the Profile group" highlight="18"
185
185
{
@@ -236,10 +236,10 @@ See [Format text](/create/text) and [Format code](/create/code) for more informa
236
236
237
237
## Publish your changes
238
238
239
-
Your changes are published based on the branch you are working on:
239
+
The branch that you work on determines how the editor publishes your changes:
240
240
241
241
***Deployment branch**: Publishing updates your live site immediately.
242
-
***Other branches**: Publishing creates a pull request so you can review changes before they are deployed to production.
242
+
***Other branches**: Publishing creates a pull request so you can review changes before deploying them to production.
243
243
244
244
<Frame>
245
245
<img
@@ -266,10 +266,10 @@ Pull requests let you propose changes from your branch so that other people can
266
266
267
267
<Steps>
268
268
<Steptitle="Save your work">
269
-
Make sure all your changes are saved on your branch using **Save Changes**.
269
+
Select **Save Changes** to save all changes on your branch.
270
270
</Step>
271
271
<Steptitle="Create the pull request">
272
-
Select **Publish Pull Request**in the top-right corner of the editor.
272
+
Select **Publish Pull Request**from the editor toolbar.
0 commit comments