diff --git a/account-management/account-settings.md b/account-management/account-settings.md
index e620fde0..e19213cb 100644
--- a/account-management/account-settings.md
+++ b/account-management/account-settings.md
@@ -7,7 +7,7 @@ description: View and manage the settings for your personal GitBook account.
You can manage your login details, third-party login options, GitBook subdomain, interface theme, notification, integrations and API access tokens.
-
Your personal settings page.
+
Your personal settings page.
### How to access your personal account settings
diff --git a/account-management/billing-faq/cancelling-a-plan.md b/account-management/billing-faq/cancelling-a-plan.md
index ce8564fa..7b9e6ca6 100644
--- a/account-management/billing-faq/cancelling-a-plan.md
+++ b/account-management/billing-faq/cancelling-a-plan.md
@@ -9,7 +9,7 @@ Only administrators can access an organization’s billing settings to cancel a
If your mind is made up, here’s how to cancel your plan:
-1. Go to the organization’s settings page. You can click on the settings icon at the bottom of the sidebar and then click on **\[organization name] settings** to get there.
+1. Go to the organization’s settings page. You can click on the settings icon at the bottom of the sidebar and then click on **\[organization name] settings** to get there.
2. Click on the **billing** tab. This will take you to a billing page hosted on Stripe, our payment processor.
diff --git a/account-management/cancelling-a-plan.md b/account-management/cancelling-a-plan.md
index 8ce20a3d..21b143cb 100644
--- a/account-management/cancelling-a-plan.md
+++ b/account-management/cancelling-a-plan.md
@@ -11,7 +11,7 @@ Here’s how to cancel your plan:
1. Go to the organization’s settings page. You can click on the settings
-
+
icon at the bottom of the sidebar and then click on **\[organization name] settings** to get there.
2. Click on the **billing** tab. This will take you to a billing page hosted on Stripe, our payment processor.
diff --git a/account-management/organization-settings.md b/account-management/organization-settings.md
index 4195ccfa..4f7f1156 100644
--- a/account-management/organization-settings.md
+++ b/account-management/organization-settings.md
@@ -6,7 +6,7 @@ icon: sitemap
View and manage the settings for your GitBook organization. These include member management, sign-in methods, integrations, billing and plans.
-
Your organization settings page.
+
Your organization settings page.
### How to access the settings for an organization
diff --git a/account-management/plans/community/sponsored-site-plan.md b/account-management/plans/community/sponsored-site-plan.md
index d2d0327e..a6b15b32 100644
--- a/account-management/plans/community/sponsored-site-plan.md
+++ b/account-management/plans/community/sponsored-site-plan.md
@@ -10,7 +10,7 @@ description: >-
This site plan is only available to users on our [community plan](./).
{% endhint %}
-
Learn more about the sponsored site plan in GitBook.
+
Learn more about the sponsored site plan in GitBook.
The sponsored site plan lets you access all of GitBook’s best docs site features at no cost while displaying a small, relevant ad in the corner of your documentation site. Each view generates revenue for you, turning your documentation into a source of income.
diff --git a/account-management/sso-and-saml/README.md b/account-management/sso-and-saml/README.md
index dcc8c1f5..20881332 100644
--- a/account-management/sso-and-saml/README.md
+++ b/account-management/sso-and-saml/README.md
@@ -13,7 +13,7 @@ When you create or manage your organisation, you can add a list of email domains
You can enable email domain SSO in the ’SSO’ section of your organization settings; enter a comma-separated list of email domains you’d like to allow SSO access for and you’re good to go.
-
Set up SSO for your organization.
+
Set up SSO for your organization.
{% hint style="info" %}
Anyone who joins via an SSO email domain will default to guest access, you can change their role at any time in the members section of your organization settings.
diff --git a/api-references/openapi/add-an-openapi-specification.md b/api-references/openapi/add-an-openapi-specification.md
index e50ddbbf..bdb827ee 100644
--- a/api-references/openapi/add-an-openapi-specification.md
+++ b/api-references/openapi/add-an-openapi-specification.md
@@ -8,7 +8,7 @@ description: >-
If you have an OpenAPI spec, you can add it to your organization by uploading the file directly, linking to a hosted URL, or using the [GitBook CLI](broken-reference).
-
+
### How to add a specification
@@ -20,7 +20,7 @@ If you have an OpenAPI spec, you can add it to your organization by uploading th
* Enter a URL to a hosted spec
* Use the CLI to publish the spec
-
Add an OpenAPI specification modal.
+
Add an OpenAPI specification modal.
### Update your specification
diff --git a/api-references/openapi/insert-api-reference-in-your-docs.md b/api-references/openapi/insert-api-reference-in-your-docs.md
index b19f69d3..f42209b3 100644
--- a/api-references/openapi/insert-api-reference-in-your-docs.md
+++ b/api-references/openapi/insert-api-reference-in-your-docs.md
@@ -16,7 +16,7 @@ Endpoints added from your spec will continue to be updated anytime your spec is
After you’ve [added your OpenAPI spec](add-an-openapi-specification.md), you can generate endpoint pages by inserting an **OpenAPI Reference** in the table of contents of a Space.
-
Insert API References in the table of contents of a Space.
+
Insert API References in the table of contents of a Space.
{% stepper %}
{% step %}
diff --git a/collaboration/change-requests.md b/collaboration/change-requests.md
index 05a8fab2..a0039535 100644
--- a/collaboration/change-requests.md
+++ b/collaboration/change-requests.md
@@ -9,7 +9,7 @@ A change request is a copy of your main content. It comes from the simple concep
In a change request, you can edit, update and delete elements of your content, request reviews on your changes, then merge them back into your main version to apply all the changes you made.
-
Edit your content through change requests.
+
Edit your content through change requests.
### Creating a change request
@@ -120,4 +120,4 @@ If you don’t want to choose between versions, you can resolve a merge conflict
If you decide not to merge a change request and want to remove it from the queue, you can archive it.
-To archive a change request, first open it up. Then click the **Actions menu** next to the change request’s title and choose **Archive**. You can find and reopen archived change requests later by opening the **Change Requests** menu and selecting the **Archived** tab.
+To archive a change request, first open it up. Then click the **Actions menu** next to the change request’s title and choose **Archive**. You can find and reopen archived change requests later by opening the **Change Requests** menu and selecting the **Archived** tab.
diff --git a/collaboration/collaboration/change-requests.md b/collaboration/collaboration/change-requests.md
index 646cf53b..d88a113b 100644
--- a/collaboration/collaboration/change-requests.md
+++ b/collaboration/collaboration/change-requests.md
@@ -6,7 +6,7 @@ description: Learn about editing with change requests
-
The change requests panel
+
The change requests panel
@@ -26,7 +26,7 @@ In a space that is **locked** for live edits, hit the ’Edit’ button in the s
-
Click the "Edit" button in the top right corner to start a change request
+
Click the "Edit" button in the top right corner to start a change request
@@ -42,7 +42,7 @@ Once you’re happy with your changes, you can **submit** the change request.
-
Submit your change request for review in the bottom right corner of the editor
+
Submit your change request for review in the bottom right corner of the editor
diff --git a/collaboration/collaboration/live-edits.md b/collaboration/collaboration/live-edits.md
index 547bd05f..4be5676a 100644
--- a/collaboration/collaboration/live-edits.md
+++ b/collaboration/collaboration/live-edits.md
@@ -26,7 +26,7 @@ You can lock or unlock space for live edits by selecting ’Unlock live edits’
-
Unlock live edits from the space actions menu
+
Unlock live edits from the space actions menu
diff --git a/collaboration/comments.md b/collaboration/comments.md
index 8ee8b8aa..b4b668c4 100644
--- a/collaboration/comments.md
+++ b/collaboration/comments.md
@@ -9,7 +9,7 @@ Comments allow you to provide feedback around specific pieces of content — wit
### Add a comment
-You can open the comments panel by clicking on the **Comments** button in the [space header](../resources/gitbook-ui.md#space-header).
+You can open the comments panel by clicking on the **Comments** button in the [space header](../resources/gitbook-ui.md#space-header).
Adding a comment here will attach a comment to the entire page. You can also comment on a specific block by hovering over a block and clicking the content icon that appears on the right.
diff --git a/collaboration/live-edits.md b/collaboration/live-edits.md
index 38115569..da63050c 100644
--- a/collaboration/live-edits.md
+++ b/collaboration/live-edits.md
@@ -13,7 +13,7 @@ GitBook supports live collaboration, meaning you’ll be able to work on the sam
### Toggling live edit mode
-You can toggle live edit mode in a space by selecting **Lock live edits** or **Unlock live edits** from the [space header’s](../resources/gitbook-ui.md#space-header) **Actions menu** .
+You can toggle live edit mode in a space by selecting **Lock live edits** or **Unlock live edits** from the [space header’s](../resources/gitbook-ui.md#space-header) **Actions menu** .
When a space is in **Live edits** mode, the space header will show the **Editor** tab. When it is in **Locked live edits** mode, the space header will show a **Read-only** tab. When the Read-only tab appears in the space header, you will need to open a change request to edit the content of the page.
diff --git a/collaboration/pdf-export.md b/collaboration/pdf-export.md
index c210d5eb..d8aa4c97 100644
--- a/collaboration/pdf-export.md
+++ b/collaboration/pdf-export.md
@@ -23,14 +23,14 @@ Note that links across spaces are not currently supported when exporting interna
#### Export an individual page
-1. Open the page you want to export, then open the page’s [Actions menu](../resources/gitbook-ui.md#the-actions-menu) next to the page title.
+1. Open the page you want to export, then open the page’s [Actions menu](../resources/gitbook-ui.md#the-actions-menu) next to the page title.
2. Select **Export to PDF > Current page**.
3. Wait for the page to load, then click the **Print or save as PDF** button in the upper right to open your browsers Print menu.
4. From here, you can save the page as a PDF or open it in your PDF viewer using the typical process for your browser.
#### Export an entire space
-1. Open the[ Actions menu](../creating-content/content-structure/) next to the page title and choose **Export as PDF > All pages**. Alternatively, open the space’s **Actions menu** in the [space header](../resources/gitbook-ui.md#space-header) and choose **Export as PDF** in the drop-down menu.\
+1. Open the[ Actions menu](../creating-content/content-structure/) next to the page title and choose **Export as PDF > All pages**. Alternatively, open the space’s **Actions menu** in the [space header](../resources/gitbook-ui.md#space-header) and choose **Export as PDF** in the drop-down menu.\
\
&#xNAN;_Note: This action is not available within a change request._
2. Wait for the page to load, then click the **Print or save as PDF** button in the upper right to open your browsers Print menu.
diff --git a/collaboration/share.md b/collaboration/share.md
index 498dcc2e..4e0aa5e3 100644
--- a/collaboration/share.md
+++ b/collaboration/share.md
@@ -5,7 +5,7 @@ description: Collaborate with your teammates on spaces, collections and more
# Inviting your team
-
Invite your team to GitBook to collaborate on pages, spaces, and published sites.
+
Invite your team to GitBook to collaborate on pages, spaces, and published sites.
### Sharing a space or collection
@@ -45,4 +45,4 @@ If you don’t want to use email to invite someone to your content, or want to i
When you share this link, anyone who clicks on it will be able to sign up, join your organization as a [guest](../account-management/member-management/roles.md#guest-role), and get access to just this single space and its content.
-You can revoke the link at any time by opening the **Actions menu** next to the link and choosing **Revoke**.
+You can revoke the link at any time by opening the **Actions menu** next to the link and choosing **Revoke**.
diff --git a/creating-content/blocks/README.md b/creating-content/blocks/README.md
index 0d523021..26e4065c 100644
--- a/creating-content/blocks/README.md
+++ b/creating-content/blocks/README.md
@@ -7,7 +7,7 @@ icon: square-dashed-circle-plus
GitBook is a block-based editor, meaning you can add different kinds of blocks to your content — from standard text and images to interactive blocks. Your pages can include any combination of blocks you want, and there’s no limit to the number of blocks you can have on a page.
-
GitBook's built in content blocks.
+
GitBook's built in content blocks.
### Inserting a new content block
@@ -41,7 +41,7 @@ Once selected, you can:
By making your blocks full width, you can create a clear visual hierarchy in your content, or simply give more space to content that needs it.
-To make a block full width, click on the **Options menu** next to your block and select **Full width**. This feature is available for the following block types:
+To make a block full width, click on the **Options menu** next to your block and select **Full width**. This feature is available for the following block types:
* Code Blocks
* Image blocks
diff --git a/creating-content/blocks/cards.md b/creating-content/blocks/cards.md
index 05dfb821..79e036f4 100644
--- a/creating-content/blocks/cards.md
+++ b/creating-content/blocks/cards.md
@@ -14,7 +14,7 @@ You can adjust [switch between medium or large cards](cards.md#card-size) and li
### Adding links
-Hover over a card and open its **Options menu** . Here you can add a target link, so users can jump directly to a location when they click the card.
+Hover over a card and open its **Options menu** . Here you can add a target link, so users can jump directly to a location when they click the card.
{% hint style="success" %}
When creating cards, we recommend you use **target links instead of hyperlinks**. With a target link, your readers can click anywhere on the card to access the linked URL.
@@ -22,7 +22,7 @@ When creating cards, we recommend you use **target links instead of hyperlinks**
### Adding images
-Hover over a card and open its **Options menu** . Here you can add a cover image to your card. Alternatively, just click the **Add cover image** option on the card itself.
+Hover over a card and open its **Options menu** . Here you can add a cover image to your card. Alternatively, just click the **Add cover image** option on the card itself.
This will open the **Select file** modal. Here you can drag and drop a new image into this, or use an image file you’ve previously uploaded to your space.
@@ -30,9 +30,9 @@ This will open the **Select file** modal. Here you can drag and drop a new imag
GitBook will automatically crop landscape images to a 16:9 ratio on desktop and mobile. If the images you upload are portrait or have a 1:1 ratio, they will be cropped to 16:9 on desktop and display as square or portrait on mobile.
-
On desktop, all card images will display in a landscape 16:9 ratio, regardless of their dimensions. We recommend using the same dimensions for consistency.
+
On desktop, all card images will display in a landscape 16:9 ratio, regardless of their dimensions. We recommend using the same dimensions for consistency.
-
On mobile, square or portrait images will displayed as shown on the left. Landscape images will be displayed as shown on the right.
+
On mobile, square or portrait images will displayed as shown on the left. Landscape images will be displayed as shown on the right.
To keep things consistent across desktop and mobile, we recommend uploading all the images for your cards in a 16:9 format (e.g. 1920px x 1080px).
@@ -40,8 +40,8 @@ If you want your cards to adapt their layout depending on the screen size, we’
### Changing the size of cards
-You can select the card size by opening the **Options menu** to the left of your card block. The **Medium** option creates three cards in one horizontal line, while the **Large** option shows two larger cards on each line.
+You can select the card size by opening the **Options menu** to the left of your card block. The **Medium** option creates three cards in one horizontal line, while the **Large** option shows two larger cards on each line.
{% hint style="info" %}
-You can make card blocks [span the full width of your window](./#full-width-blocks) by clicking on the **Options menu** next to the block and choosing **Full width**.
+You can make card blocks [span the full width of your window](./#full-width-blocks) by clicking on the **Options menu** next to the block and choosing **Full width**.
{% endhint %}
diff --git a/creating-content/blocks/code-block.md b/creating-content/blocks/code-block.md
index 2441a402..4fdee9dc 100644
--- a/creating-content/blocks/code-block.md
+++ b/creating-content/blocks/code-block.md
@@ -59,12 +59,12 @@ greeting.("Anna")
{% endtabs %}
{% hint style="info" %}
-You can make code blocks [span the full width of your window](./#full-width-blocks) by clicking on the **Options menu** next to the block and choosing **Full width**.
+You can make code blocks [span the full width of your window](./#full-width-blocks) by clicking on the **Options menu** next to the block and choosing **Full width**.
{% endhint %}
### Code block options
-When you click on the **Options menu** next to the code block, or the **Actions menu** in the block itself, you’ll see a number of options you can set.
+When you click on the **Options menu** next to the code block, or the **Actions menu** in the block itself, you’ll see a number of options you can set.
#### Set syntax…
diff --git a/creating-content/blocks/columns.md b/creating-content/blocks/columns.md
index a14b4a90..02f92e80 100644
--- a/creating-content/blocks/columns.md
+++ b/creating-content/blocks/columns.md
@@ -16,6 +16,6 @@ Integrate your documentation right into your product experience, or give users a
{% endcolumn %}
{% column %}
-
+
{% endcolumn %}
{% endcolumns %}
diff --git a/creating-content/blocks/drawing.md b/creating-content/blocks/drawing.md
index f59f462a..8a922c4a 100644
--- a/creating-content/blocks/drawing.md
+++ b/creating-content/blocks/drawing.md
@@ -12,7 +12,7 @@ GitBook stores drawings as special SVG files in the space. Those files have an e
### Example of a drawing block
-
+
### Draw with GitBook AI
diff --git a/creating-content/blocks/heading.md b/creating-content/blocks/heading.md
index 31f03b2c..76c484fa 100644
--- a/creating-content/blocks/heading.md
+++ b/creating-content/blocks/heading.md
@@ -22,7 +22,7 @@ If you want to link to a particular anchor from a page within your GitBook space
By default, the anchor link will be identical to the text in your header. If you plan to link to that URL outside of GitBook, changing the header in future will break the anchor link. The link will then take visitors to the top of the page, rather than the anchor location.
-To avoid this, you can manually set the anchor link by opening the **Options menu** for the header, then choosing **Edit anchor**. You can then enter the anchor link you wish to use — this will remain the anchor even if you change the header itself.
+To avoid this, you can manually set the anchor link by opening the **Options menu** for the header, then choosing **Edit anchor**. You can then enter the anchor link you wish to use — this will remain the anchor even if you change the header itself.
### Heading examples
diff --git a/creating-content/blocks/hint.md b/creating-content/blocks/hint.md
index 9d388221..aa3ba3c0 100644
--- a/creating-content/blocks/hint.md
+++ b/creating-content/blocks/hint.md
@@ -8,7 +8,7 @@ description: >-
Hints are a great way to bring the reader’s attention to specific elements in your documentation, such as tips, warnings, and other important information.
-There are four different hint styles — you can change the style by clicking the colored icon, or by opening the block’s **Options menu** and selecting the style you want.
+There are four different hint styles — you can change the style by clicking the colored icon, or by opening the block’s **Options menu** and selecting the style you want.
Hint blocks support [inline content](../formatting/inline.md) and [formatting](../formatting/), as well some specific block types. To see which block types you can use in a hint, hit `/` on an empty line and check the [insert palette](./#inserting-a-new-content-block).
@@ -35,7 +35,7 @@ Hint blocks support [inline content](../formatting/inline.md) and [formatting](.
This is a line
-This is an inline image
+This is an inline image
* This is a second line using an unordered list and color
{% endhint %}
@@ -68,7 +68,7 @@ To add a heading to your hint, you need to create a heading block as the the fir
This is a line
-This is an inline image
+This is an inline image
- This is a second line using an unordered list and color
{% endhint %}
diff --git a/creating-content/blocks/insert-files.md b/creating-content/blocks/insert-files.md
index 4d9096c7..a85b4e21 100644
--- a/creating-content/blocks/insert-files.md
+++ b/creating-content/blocks/insert-files.md
@@ -34,11 +34,11 @@ You can also add files to your space when you add an [image block](insert-images
### Renaming a file
-To rename a file, open the **Actions menu** for the file, and click **Edit**. In the dialog prompt, enter the new name of your file.
+To rename a file, open the **Actions menu** for the file, and click **Edit**. In the dialog prompt, enter the new name of your file.
### Deleting a file
-To delete a file, open the **Actions menu** for the file and click **Delete**. After confirming in the dialog that you’re sure you want to delete the file, your file will be deleted.
+To delete a file, open the **Actions menu** for the file and click **Delete**. After confirming in the dialog that you’re sure you want to delete the file, your file will be deleted.
{% hint style="warning" %}
**Note:** Make sure you update any pages that included your deleted file! File blocks that reference a deleted file will show an empty block, or _Could not load image_ error.
@@ -48,7 +48,7 @@ To delete a file, open the **Actions menu** for the file and click **Replace**. In the file replacement dialog that appears, select the new file and wait for the upload indicator to complete. Your file will automatically update everywhere it appeared in your space.
+To replace a file, open the **Actions menu** for the file and click **Replace**. In the file replacement dialog that appears, select the new file and wait for the upload indicator to complete. Your file will automatically update everywhere it appeared in your space.
This can be helpful if, for example, you’ve had a major product redesign and need to update outdated UI screenshots that appear on multiple pages. Replacing the original file would update the screenshot everywhere in your space, saving you time and effort.
diff --git a/creating-content/blocks/insert-images.md b/creating-content/blocks/insert-images.md
index cbcc0315..d7ff4fd6 100644
--- a/creating-content/blocks/insert-images.md
+++ b/creating-content/blocks/insert-images.md
@@ -14,7 +14,7 @@ You can insert images into your page, then choose their size and whether to alig
### Example of an image block
-
+
### Uploading an image
@@ -31,15 +31,15 @@ GitBook allows you to upload images up to 100MB per file.
#### Create an image gallery
-Adding more than one image to an image block will create a gallery. To do this, open the block’s **Options menu** and choose **Add images…** to open the **Select images** side panel again.
+Adding more than one image to an image block will create a gallery. To do this, open the block’s **Options menu** and choose **Add images…** to open the **Select images** side panel again.
-To delete an image from a gallery, open the **Actions menu** on the image you want to delete and press the **Delete ⌫** key.
+To delete an image from a gallery, open the **Actions menu** on the image you want to delete and press the **Delete ⌫** key.
### Adding images for light & dark mode
You can set different images for the light and dark mode versions of your published site. GitBook will automatically display the correct image depending on the mode your visitor is in.
-To add an image for dark mode, hover over your image, open the **Actions menu** and click **Replace image** .
+To add an image for dark mode, hover over your image, open the **Actions menu** and click **Replace image** .
In the drop-down menu, choose **Add image for Dark mode**. Once you’ve set this, you can replace either image from this same menu.
@@ -98,9 +98,9 @@ and text after the image
### Resizing
-To resize your image, hover over it and open the **Actions menu** . Click the **Size** button to change the size of your image from the available options.
+To resize your image, hover over it and open the **Actions menu** . Click the **Size** button to change the size of your image from the available options.
-
Resize an image
+
Resize an image
- **Small** – 25% of the image size
- **Medium** – 50% of the image size
@@ -114,7 +114,7 @@ If your image is wider than the editor, GitBook will limit the image’s width t
{% endhint %}
{% hint style="info" %}
-You can make image blocks [span the full width of your window](./#full-width-blocks) by clicking on the **Options menu** next to the block and choosing **Full width**.
+You can make image blocks [span the full width of your window](./#full-width-blocks) by clicking on the **Options menu** next to the block and choosing **Full width**.
{% endhint %}
### Resizing images through Git Sync
@@ -132,7 +132,7 @@ Valid variants for specifying the image dimensions are:\
By default, image blocks will show your image at its full size, aligned centrally.
-To change the alignment of an image, open the block’s **Options menu** and choose the alignment you want. This will only affect images that are narrower than the editor, or images you’ve [resized](insert-images.md#resizing).
+To change the alignment of an image, open the block’s **Options menu** and choose the alignment you want. This will only affect images that are narrower than the editor, or images you’ve [resized](insert-images.md#resizing).
### Representation in Markdown
diff --git a/creating-content/blocks/table.md b/creating-content/blocks/table.md
index 8c51be9a..34f17fbe 100644
--- a/creating-content/blocks/table.md
+++ b/creating-content/blocks/table.md
@@ -47,7 +47,7 @@ Tables that are wider than the editor container will be horizontally scrollable.
### Column options
-To reorder columns, click and drag on the drag handle at the top of the column you want to move.
+To reorder columns, click and drag on the drag handle at the top of the column you want to move.
You can add new columns by clicking the **Add column** button that appears when you hover over the right edge of the table.
@@ -55,7 +55,7 @@ Inside the **Column options** menu you can also switch automatic sizing on and o
### Row options
-Hover over the row and click the **Row options** button that appears on the left of it to open the **Row options** menu. You’ll see a number of options:
+Hover over the row and click the **Row options** button that appears on the left of it to open the **Row options** menu. You’ll see a number of options:
* **Open row:** Open the row in a modal that shows all of its data. Here you can quickly change row types, edit data, and see data in hidden columns.
* **Insert above/below:** Add a new row above or below the currently-selected row.
diff --git a/creating-content/blocks/tabs.md b/creating-content/blocks/tabs.md
index eaf2ac87..2887f2dc 100644
--- a/creating-content/blocks/tabs.md
+++ b/creating-content/blocks/tabs.md
@@ -12,7 +12,7 @@ Each tab can contain multiple other blocks, of any type. So you can add code blo
### Add or delete tabs
-To add a new tab to a tab block, hover over the edge of a tab and click the `+` button that appears. To delete a tab, open the tab’s **Options menu** then select **Delete**.
+To add a new tab to a tab block, hover over the edge of a tab and click the `+` button that appears. To delete a tab, open the tab’s **Options menu** then select **Delete**.
### Example
diff --git a/creating-content/broken-links.md b/creating-content/broken-links.md
index 8da98fd0..dd0bf4c1 100644
--- a/creating-content/broken-links.md
+++ b/creating-content/broken-links.md
@@ -7,7 +7,7 @@ description: Find and replace broken relative links across your spaces
{% include "../.gitbook/includes/pro-and-enterprise-hint.md" %}
-
The Broken links panel that you can open on the right of a space to check for broken internal links.
+
The Broken links panel that you can open on the right of a space to check for broken internal links.
You can add different [types of links](formatting/inline.md#links) to your pages in GitBook. If someone has broken a [relative link](formatting/inline.md#relative-links) while making a change request by updating it or changing its location, you’ll see a notification letting you know there’s something to fix.
diff --git a/creating-content/content-structure/collection.md b/creating-content/content-structure/collection.md
index 74e1f813..f5edfc27 100644
--- a/creating-content/content-structure/collection.md
+++ b/creating-content/content-structure/collection.md
@@ -15,7 +15,7 @@ Click the **+** button next to the **Spaces** header in the sidebar to create a
### Move a collection
-You can move a collection by opening the **Actions menu** , selecting **Move collection to…** and choosing a destination. Alternatively, you can drag and drop collections in the sidebar to move or reorder them.\
+You can move a collection by opening the **Actions menu** , selecting **Move collection to…** and choosing a destination. Alternatively, you can drag and drop collections in the sidebar to move or reorder them.\
\
You can move collections into other collections — or even to other organizations, if you have an [admin role](../../account-management/member-management/roles.md) in both.
@@ -25,11 +25,11 @@ You can nest collections inside each other, creating a collection -> sub-collect
Open a collection and you can click **New collection** from the collection’s main page to create a sub-collection.
-To move one collection into another, click **Move collection to…** from the collection’s **Action menu** and then choose its new location. Alternatively, you can drag and drop the collection to its new location.
+To move one collection into another, click **Move collection to…** from the collection’s **Action menu** and then choose its new location. Alternatively, you can drag and drop the collection to its new location.
### How to delete a collection
-You can delete a collection by opening its **Actions menu** and selecting **Delete**.
+You can delete a collection by opening its **Actions menu** and selecting **Delete**.
{% hint style="danger" %}
**Deleting a collection is final**, but spaces inside a deleted collection will move to the **Trash** and can be restored up to seven days after deletion. You can access the Trash from the bottom of the sidebar.
diff --git a/creating-content/content-structure/page.md b/creating-content/content-structure/page.md
index b02e0287..76a6d1d0 100644
--- a/creating-content/content-structure/page.md
+++ b/creating-content/content-structure/page.md
@@ -16,7 +16,7 @@ You can create as many pages as you need in a space. They’re all visible on th
When in [live edit](../../collaboration/live-edits.md) mode or in a [change request](../../collaboration/change-requests.md), you can create a new page by clicking **Add new...** > **Page** at the bottom of your table of contents. Alternatively, you can hover between pages in the table of contents and click the **+** icon that appears.
-
An empty page in GitBook. You can see it listed in the table of contents on the left-hand side.
+
An empty page in GitBook. You can see it listed in the table of contents on the left-hand side.
### Can’t see the option to create a new page?
@@ -42,7 +42,7 @@ You can nest pages by dragging and dropping a page below an other in the table o
When you change the title of a page, the page’s slug (the part at the very end of the URL, e.g. `/hello-world`) will also change — unless you’ve manually set the page’s slug previously.
-You can change the title and the slug of a page at any time by clicking opening the page’s **Action menu** and choosing **Rename**.
+You can change the title and the slug of a page at any time by clicking opening the page’s **Action menu** and choosing **Rename**.
#### Page groups
@@ -52,7 +52,7 @@ You can create a new page group by clicking **Add new...** > **Group** at the bo
Page groups can only live at the **top level** of the table of contents. You cannot nest page groups inside page groups.
-To change the title and slug of a page group, click the **Action menu** icon next to the group title in the table of contents and choose **Rename**.
+To change the title and slug of a page group, click the **Action menu** icon next to the group title in the table of contents and choose **Rename**.
#### External links
@@ -72,7 +72,7 @@ In the **Page options** menu you can customize the look and feel of a selected p
**Layout**
-You can open the **Page options** menu or change a page’s cover by hovering over the page title. You’ll see the buttons appear just above the page title.
+You can open the **Page options** menu or change a page’s cover by hovering over the page title. You’ll see the buttons appear just above the page title.
In the **Page options** side panel, you can select how each page is displayed to those who visit your **published** content. There are three layout presets to choose from, or you can create a custom layout.
@@ -88,7 +88,7 @@ Each layout preset will toggle on or off each of the following parts of the page
You can decide which pages you would like to show/hide in your published documentation, while also deciding if you would like the page to be indexed in your published doc’s search, and/or indexed by search engines.
-You can hide a page or group of pages from your site's table of contents by opening the page’s **Actions menu** and toggling **Hide page**.
+You can hide a page or group of pages from your site's table of contents by opening the page’s **Actions menu** and toggling **Hide page**.
If hidden the following will appear in the front matter of the markdown file when using Git Sync:
@@ -99,15 +99,15 @@ hidden: true
### Page covers
-You can also set a page cover for each page of your documentation. When you click the **Page cover** option, a default cover will be added immediately. From here, you can:
+You can also set a page cover for each page of your documentation. When you click the **Page cover** option, a default cover will be added immediately. From here, you can:
* **Change the cover image**
Hover over the page cover and click **Change cover**, then select or upload an image. Based on how we currently display page covers, 1990x480 pixels is the ideal size.
* **Reposition the cover image**
- Hover over the page cover and open the **Actions menu** . Click **Reposition**, then drag the image as you wish and click **Save**.
+ Hover over the page cover and open the **Actions menu** . Click **Reposition**, then drag the image as you wish and click **Save**.
* **Remove the cover image**\
- Hover over the page cover and open the **Actions menu** , then click **Remove**.
+ Hover over the page cover and open the **Actions menu** , then click **Remove**.
* **Full width and hero width**\
- You can change the style of your page cover to span the full width of your screen or just the width of your content. Hover over the page cover and open the **Actions menu** , then choose your preferred option from the menu.
+ You can change the style of your page cover to span the full width of your screen or just the width of your content. Hover over the page cover and open the **Actions menu** , then choose your preferred option from the menu.
diff --git a/creating-content/content-structure/space.md b/creating-content/content-structure/space.md
index 2b78b3ae..e66cd7b9 100644
--- a/creating-content/content-structure/space.md
+++ b/creating-content/content-structure/space.md
@@ -6,7 +6,7 @@ description: Organize the content you create and publish into spaces
A space is a project that lets you work on a collection of related pages. They allow you to write content, organize pages, add integrations and more.
-
+
### Create a space
@@ -16,19 +16,19 @@ You can edit a space’s name by hovering over the name in the [space header](..
### Duplicate a space
-To duplicate a space, open that space's **Action menu** in the sidebar and select **Duplicate**.
+To duplicate a space, open that space's **Action menu** in the sidebar and select **Duplicate**.
Duplicating a space will create a copy of the source space, in the same location (organization, collection, sub-collection, etc.).
### Move a space
-You can move a space by opening the space’s **Action menu** in the sidebar, selecting **Move space to…** and choosing a destination. Alternatively, you can drag and drop spaces in the sidebar to move or reorder them.\
+You can move a space by opening the space’s **Action menu** in the sidebar, selecting **Move space to…** and choosing a destination. Alternatively, you can drag and drop spaces in the sidebar to move or reorder them.\
\
You can move spaces between collections or even organizations, as long as you have an [admin role](../../account-management/member-management/roles.md) in both.
### Delete a space
-You can delete a space by opening the space’s **Action menu** in the sidebar and selecting **Delete**.
+You can delete a space by opening the space’s **Action menu** in the sidebar and selecting **Delete**.
{% hint style="warning" %}
**Deleted spaces can be restored from the Trash for up to 7 days**. After this, they will be permanently deleted.
diff --git a/creating-content/formatting/README.md b/creating-content/formatting/README.md
index f5a407fc..24385ea6 100644
--- a/creating-content/formatting/README.md
+++ b/creating-content/formatting/README.md
@@ -79,7 +79,7 @@ This is [a link that starts an email to a specific address](mailto:support@gitbo
Click the color icon in the context menu, and choose a color for the text or its background.
-
+This text is orange.
diff --git a/creating-content/formatting/inline.md b/creating-content/formatting/inline.md
index ab7d5fb8..33375984 100644
--- a/creating-content/formatting/inline.md
+++ b/creating-content/formatting/inline.md
@@ -4,7 +4,7 @@ description: Use the inline palette to add images, links, math & TeX, and more
# Inline content
-
Add inline elements to your content.
+
Add inline elements to your content.
The inline palette lets you quickly add extra content to your text block without moving your hands away from the keyboard. Simply hit `/` on any text block to open the inline palette. The forward slash will be replaced by the content you choose to insert.
diff --git a/creating-content/formatting/markdown.md b/creating-content/formatting/markdown.md
index d4d16914..0a21be37 100644
--- a/creating-content/formatting/markdown.md
+++ b/creating-content/formatting/markdown.md
@@ -6,7 +6,7 @@ description: >-
# Markdown
-
Write Markdown in GitBook.
+
Write Markdown in GitBook.
GitBook’s editor allows you to create formatted content using Markdown.
diff --git a/creating-content/reusable-content.md b/creating-content/reusable-content.md
index a70a71fe..3e29d5f9 100644
--- a/creating-content/reusable-content.md
+++ b/creating-content/reusable-content.md
@@ -11,7 +11,7 @@ icon: repeat
Reusable content lets you sync content across multiple pages and spaces, so you can edit all instances of the block at the same time.
-
Create reusable content within a space.
+
Create reusable content within a space.
## Fundamentals
@@ -41,7 +41,7 @@ Currently, reusable content only appears in search results within its parent spa
### **Create reusable content**
-To create reusable content, [select one or more blocks](blocks/#selecting-blocks-and-interacting-with-selected-blocks), then open the **Actions menu** , select **Turn into**, and choose **Reusable content**. You can also give your block a name to make it easier to find and reuse later.
+To create reusable content, [select one or more blocks](blocks/#selecting-blocks-and-interacting-with-selected-blocks), then open the **Actions menu** , select **Turn into**, and choose **Reusable content**. You can also give your block a name to make it easier to find and reuse later.
Alternatively, you can select one or more blocks and then hit **Cmd + C** to open a prompt asking if you want to create reusable content.
@@ -59,13 +59,13 @@ If you’re making changes inside a change request, the content will be synced t
### **Detach reusable content**
-You can detach reusable content by opening the **Actions menu** and selecting **Detach**. Detaching will convert the content back to regular blocks.
+You can detach reusable content by opening the **Actions menu** and selecting **Detach**. Detaching will convert the content back to regular blocks.
Once detached, any changes you make to the block(s) will not be reflected across the other instances, and changes you make in those instances will not be reflected in the detached block(s). All other instances of the reusable content remain synced together.
### Delete reusable content
-You can delete reusable content from your space entirely, if you wish. Find the reusable content in the page’s table of contents, then open the **Actions menu** next to the content you’d like to delete, and select **Delete**.
+You can delete reusable content from your space entirely, if you wish. Find the reusable content in the page’s table of contents, then open the **Actions menu** next to the content you’d like to delete, and select **Delete**.
Deleting reusable content will **delete it from all pages it is used in**. This action cannot be undone.
diff --git a/creating-content/searching-your-content/README.md b/creating-content/searching-your-content/README.md
index 10a81039..02606c51 100644
--- a/creating-content/searching-your-content/README.md
+++ b/creating-content/searching-your-content/README.md
@@ -7,7 +7,7 @@ icon: magnifying-glass
# Searching content
-
Ask questions or search through your content using the built in search bar.
+
Ask questions or search through your content using the built in search bar.
Whether you’re working within the GitBook app or your visitors are reading your published content, GitBook’s search functions help to make it easy to find what you’re looking for.
diff --git a/creating-content/version-control.md b/creating-content/version-control.md
index f0f54634..f7fe7b12 100644
--- a/creating-content/version-control.md
+++ b/creating-content/version-control.md
@@ -17,7 +17,7 @@ In the Version history of a space, you can see a list of all the actions that ch
### View historical versions of content
-To view past versions of your content and see the changes that were made, click the **Version history** button in the [space header](../resources/gitbook-ui.md#space-header), or open the **Actions menu** next to the space or change request title and choose **Version history**.
+To view past versions of your content and see the changes that were made, click the **Version history** button in the [space header](../resources/gitbook-ui.md#space-header), or open the **Actions menu** next to the space or change request title and choose **Version history**.
Click on any item in the list to see how your content looked at the point this change was made. This is very similar to how you view [change requests](../collaboration/change-requests.md).
@@ -53,4 +53,4 @@ Add it at the end of your published docs URL as `/~/revisions/`
Rolling back allows you to revert a space’s content to the way it was at a previous point in time. This is helpful if you’ve accidentally made a breaking change or deleted content and need to quickly get back to a previous version of the space.
-To roll back to a previous version of your space, hover over the version in the side panel, click the **Actions button** and select **Rollback**.
+To roll back to a previous version of your space, hover over the version in the side panel, click the **Actions button** and select **Rollback**.
diff --git a/creating-content/write-and-edit-with-ai.md b/creating-content/write-and-edit-with-ai.md
index 5e6b1210..f4d16faa 100644
--- a/creating-content/write-and-edit-with-ai.md
+++ b/creating-content/write-and-edit-with-ai.md
@@ -9,7 +9,7 @@ description: Use GitBook AI to generate and build content for your page
You can use GitBook AI to create content on any empty line on your page. It can create all kinds of content — formatted in Markdown — including code samples, templates, page summaries and more.
-
Write with GitBook AI.
+
Write with GitBook AI.
### Write with GitBook AI
diff --git a/getting-started/git-sync/README.md b/getting-started/git-sync/README.md
index ba0229ef..2ee1455f 100644
--- a/getting-started/git-sync/README.md
+++ b/getting-started/git-sync/README.md
@@ -7,7 +7,7 @@ description: >-
# GitHub & GitLab Sync
-
Set up Git Sync for your GitBook space.
+
Set up Git Sync for your GitBook space.
### Overview
diff --git a/getting-started/git-sync/commits.md b/getting-started/git-sync/commits.md
index 1ed0fb56..b795dda0 100644
--- a/getting-started/git-sync/commits.md
+++ b/getting-started/git-sync/commits.md
@@ -28,7 +28,7 @@ Use the following URL format, where `spaceId` corresponds to your space’s URL:
`/`
-
Autolink setup.
+
Autolink setup.
## Customize the commit message template
diff --git a/getting-started/git-sync/enabling-github-sync.md b/getting-started/git-sync/enabling-github-sync.md
index 689c6923..951fd08c 100644
--- a/getting-started/git-sync/enabling-github-sync.md
+++ b/getting-started/git-sync/enabling-github-sync.md
@@ -8,7 +8,7 @@ description: Set up and authorize the GitHub integration for GitBook
In the space you want to sync with your GitHub repo, head to the [space header](../../resources/gitbook-ui.md#space-header) in the top right, and select **Configure**. From the provider list, select **GitHub Sync**.
-
GitHub Sync configuration options.
+
GitHub Sync configuration options.
### Authenticate with GitHub
diff --git a/getting-started/git-sync/enabling-gitlab-sync.md b/getting-started/git-sync/enabling-gitlab-sync.md
index 7ae80613..fe603f5d 100644
--- a/getting-started/git-sync/enabling-gitlab-sync.md
+++ b/getting-started/git-sync/enabling-gitlab-sync.md
@@ -8,7 +8,7 @@ description: Set up and authorize the GitLab integration for GitBook
In the space you want to sync with your GitLab repo, head to the space menu in the top right, and select **Synchronize with Git**. From the provider list, select **GitLab Sync**, and click **Configure**.
-
GitLab Sync configuration options.
+
GitLab Sync configuration options.
### Generate and enter your API access token
diff --git a/getting-started/git-sync/github-pull-request-preview.md b/getting-started/git-sync/github-pull-request-preview.md
index 38dfd3d1..9607ab7e 100644
--- a/getting-started/git-sync/github-pull-request-preview.md
+++ b/getting-started/git-sync/github-pull-request-preview.md
@@ -8,7 +8,7 @@ When you submit a pull request (PR) to a GitHub branch that has been synced to a
You can use this feature to have a final layer of checks before merging a PR, allowing you to see your changes in a non-production environment before merging it into your synced branch.
-
See a preview of your GitBook site when making a Pull Request.
+
The import panel in GitBook.
+
The import panel in GitBook.
When you create a new space, you’ll have the option to import content from the bottom sheet of the first empty page.
-Alternatively, you can always import a page or subpage by selecting **New page** > **Import new pages** in the [table of contents](../resources/gitbook-ui.md#table-of-contents), or opening the Actions menu for a page and choosing **Import subpages**.
+Alternatively, you can always import a page or subpage by selecting **New page** > **Import new pages** in the [table of contents](../resources/gitbook-ui.md#table-of-contents), or opening the Actions menu for a page and choosing **Import subpages**.
After choosing an input source, you can select the file you’d like to import.
diff --git a/getting-started/quickstart.md b/getting-started/quickstart.md
index 49dfb9a3..0b5f368c 100644
--- a/getting-started/quickstart.md
+++ b/getting-started/quickstart.md
@@ -15,7 +15,7 @@ You’ll need a GitBook account to start publishing documentation.
When you first sign up, you’ll have a chance to create a docs site from the docs site wizard. You can launch the wizard again to create a new site at any point by clicking the **+** button next to the **Docs sites** header in the sidebar.
-
Publish your first site in just a few minutes using the docs site wizard.
+
Publish your first site in just a few minutes using the docs site wizard.
The docs site wizard will take you through the flow of creating your first site. You’ll need to give your site a name, choose if you want to start from scratch with an empty site or add our sample content, and whether or not you want to publish your docs right away.
diff --git a/help/connectivity-issues.md b/help/connectivity-issues.md
index 7bbf691f..3ea98ba0 100644
--- a/help/connectivity-issues.md
+++ b/help/connectivity-issues.md
@@ -54,4 +54,4 @@ Here are a few possible causes for your connectivity issues:
Please always check [our status page](https://www.gitbookstatus.com/) to see if there are any outages to our app or the third-party services we rely on.
{% endhint %}
-If everything fails, please share the details with [GitBook Support](mailto:support@gitbook.com).
+If everything fails, please share the details with [GitBook Support](mailto:support@gitbook.com).
diff --git a/integrations/install-an-integration.md b/integrations/install-an-integration.md
index 56a905d7..55379a7e 100644
--- a/integrations/install-an-integration.md
+++ b/integrations/install-an-integration.md
@@ -13,7 +13,7 @@ You can install an integration in a single space, multiple spaces, or all the sp
If you install an integration in a single space, it will only work in that specific space. By installing an integration in multiple spaces, you’ll be able to perform actions across all those spaces.
-
Browse GitBook's built in integration library.
+
Browse GitBook's built in integration library.
### Install an integration in your organization
@@ -27,7 +27,7 @@ Next, click on the integration you want to install. Certain integrations work ca
On this screen you can select the areas you would like to install your integration in.
-
Choose an area to install an integration in.
+
Choose an area to install an integration in.
#### 3. Configure your integration
diff --git a/integrations/integrations-beta/github-entities.md b/integrations/integrations-beta/github-entities.md
index 18144f53..aed5d712 100644
--- a/integrations/integrations-beta/github-entities.md
+++ b/integrations/integrations-beta/github-entities.md
@@ -47,25 +47,25 @@ To configure the GitHub Entities integration, you’ll need to both authenticate
1. **Install the GitHub Entities integration in GitBook**
-
Install the GitHub Entities integration
+
Install the GitHub Entities integration
2. **Install the GitBook Entities app to GitHub**
To configure the GitHub Entities integration correctly, you’ll need to [install the GitBook Entities](https://github.com/apps/gitbook-entities/) app into your GitHub Account.
-
Install the GitBook Entities ap to GitHub
+
Install the GitBook Entities ap to GitHub
3. **Select the repositories you want to sync**
-
Select repositories to index
+
Select repositories to index
4. **Authenticate your GitHub Account**
-
Authenticate your GitHub account
+
Authenticate your GitHub account
5. **Select your account in the GitBook integration’s configuration**
-
Select your GitHub account
+
Select your GitHub account
{% hint style="warning" %}
GitHub Entities will index any and all of the repositories you grant it access to. If you’d only like to index a select few repositories, make sure to configure them as you see in step 3 above.
diff --git a/product-tour/git-sync/monorepos.md b/product-tour/git-sync/monorepos.md
index adc99e45..92b09873 100644
--- a/product-tour/git-sync/monorepos.md
+++ b/product-tour/git-sync/monorepos.md
@@ -6,7 +6,7 @@ GitBook can synchronize multiple directories from the same repository with multi
-
Monorepo preview
+
Monorepo preview
diff --git a/product-tour/navigation.md b/product-tour/navigation.md
index 5280748a..64a98e98 100644
--- a/product-tour/navigation.md
+++ b/product-tour/navigation.md
@@ -154,7 +154,7 @@ Page actions are located next to the page title. The type of actions available w
-
Page options menu
+
Page options menu
diff --git a/product-tour/searching-your-content/lens.md b/product-tour/searching-your-content/lens.md
index ab8ae2f3..619dc2e1 100644
--- a/product-tour/searching-your-content/lens.md
+++ b/product-tour/searching-your-content/lens.md
@@ -40,7 +40,7 @@ Then, click on the GitBook AI tab. You’ll see a number of suggested questions
-
Ask a question with GitBook AI.
+
Ask a question with GitBook AI.
@@ -48,7 +48,7 @@ For this example, lets try: "What makes change requests a powerful GitBook featu
-
GitBook AI gives you a semantic answer to your question.
+
GitBook AI gives you a semantic answer to your question.
diff --git a/product-tour/sso-and-saml/saml/README.md b/product-tour/sso-and-saml/saml/README.md
index 545313bb..b3cccd09 100644
--- a/product-tour/sso-and-saml/saml/README.md
+++ b/product-tour/sso-and-saml/saml/README.md
@@ -24,7 +24,7 @@ After configuring SSO on your IdP, you will be able to enter metadata. When the
-
+
@@ -41,7 +41,7 @@ Most SAML 2.0 compliant identity providers require the same information about th
-
+
diff --git a/product-tour/sso-and-saml/saml/sso-members-vs-non-sso.md b/product-tour/sso-and-saml/saml/sso-members-vs-non-sso.md
index f89e8eb8..9c011b65 100644
--- a/product-tour/sso-and-saml/saml/sso-members-vs-non-sso.md
+++ b/product-tour/sso-and-saml/saml/sso-members-vs-non-sso.md
@@ -4,7 +4,7 @@ Users who have created a GitBook account with an email used in your SAML Identit
-
Login with SSO screen
+
Login with SSO screen
@@ -41,6 +41,6 @@ to Organization administrators can enable SSO login for members by linking their
-
+
diff --git a/publishing-documentation/adaptive-content/README.md b/publishing-documentation/adaptive-content/README.md
index 0caf708e..09112416 100644
--- a/publishing-documentation/adaptive-content/README.md
+++ b/publishing-documentation/adaptive-content/README.md
@@ -16,7 +16,7 @@ Adaptive content helps to build a tailored documentation experience based on who
Adaptive content is slightly different from [authenticated access](../authenticated-access/), although they can work together. While authenticated access allows you to protect your docs through a login, adaptive content customizes published material based on various authentication methods — including authenticated access or those from your own app.
{% endhint %}
-
Enable adaptive content on a page, variant, or section.
+
Enable adaptive content on a page, variant, or section.
### How it works
diff --git a/publishing-documentation/adaptive-content/adapting-your-content.md b/publishing-documentation/adaptive-content/adapting-your-content.md
index ca31ccd3..58681bd5 100644
--- a/publishing-documentation/adaptive-content/adapting-your-content.md
+++ b/publishing-documentation/adaptive-content/adapting-your-content.md
@@ -38,19 +38,19 @@ You can combine multiple claims into the condition editor to match specific user
### Conditional pages
-To launch the condition editor for a page, head to the actions menu next to a page, and click “**Add condition**”. You can also launch the condition editor from a [page’s options](../../resources/gitbook-ui.md#page-options).
+To launch the condition editor for a page, head to the actions menu next to a page, and click “**Add condition**”. You can also launch the condition editor from a [page’s options](../../resources/gitbook-ui.md#page-options).
-You can see which pages in your space have conditions set if the page has a page condition icon next to it.
+You can see which pages in your space have conditions set if the page has a page condition icon next to it.
### Conditional variants
-To launch the condition editor for a variant, head to the actions menu next to a variant, and click “**Add condition**”.
+To launch the condition editor for a variant, head to the actions menu next to a variant, and click “**Add condition**”.
-You can see which variants in your docs have conditions set if the variant has a page condition icon next to it.
+You can see which variants in your docs have conditions set if the variant has a page condition icon next to it.
### Conditional sections
-To launch the condition editor for a section, head to the actions menu next to a section, and click “**Add condition**”.
+To launch the condition editor for a section, head to the actions menu next to a section, and click “**Add condition**”.
-You can see which sections in your docs have conditions set if the section has a page condition icon next to it.
+You can see which sections in your docs have conditions set if the section has a page condition icon next to it.
diff --git a/publishing-documentation/adaptive-content/enabling-adaptive-content.md b/publishing-documentation/adaptive-content/enabling-adaptive-content.md
index d1175cd2..bf1898d0 100644
--- a/publishing-documentation/adaptive-content/enabling-adaptive-content.md
+++ b/publishing-documentation/adaptive-content/enabling-adaptive-content.md
@@ -12,7 +12,7 @@ Before you’re able to pass user data to GitBook, you’ll need to configure yo
Head to your [site’s settings](../site-settings.md), and enable “Adaptive content” from your site’s audience settings. Once enabled, you’ll get a generated “Visitor token signing key”, which you’ll need in order to continue the adaptive content setup.
-
Enable adaptive content
+
Enable adaptive content
### Set your adaptive schema
diff --git a/publishing-documentation/adaptive-content/testing-with-segments.md b/publishing-documentation/adaptive-content/testing-with-segments.md
index db7cf61a..6af249c8 100644
--- a/publishing-documentation/adaptive-content/testing-with-segments.md
+++ b/publishing-documentation/adaptive-content/testing-with-segments.md
@@ -8,11 +8,11 @@ Segments allow you to test the conditions you set by defining claims on a mock u
For example, you might want to only show a page or section to beta users. By creating a segment and defining the properties associated with this group of mock users, you can mimic a segment that is specific to the users you’re targeting.
-
The segment editor in GitBook.
+
The segment editor in GitBook.
### Create a segment
-To create a new segment, head to the condition editor, and click the settings icon next to an existing segment in the segment dropdown.
+To create a new segment, head to the condition editor, and click the settings icon next to an existing segment in the segment dropdown.
Here you’ll be able to define the data that will appear on a mock user. Because this is the data that’s being represented, the `visitor.claims` key is omitted.
@@ -28,7 +28,7 @@ To create a segment for beta users following the examples in our docs, you would
When heading back to the condition editor, selecting the beta segment we created should show that the page we’re viewing **would** be accessible to our test user.
-
Testing a segment in GitBook.
+
Testing a segment in GitBook.
### Detected segments
diff --git a/publishing-documentation/authenticated-access/README.md b/publishing-documentation/authenticated-access/README.md
index 0752676c..b7bb4fc6 100644
--- a/publishing-documentation/authenticated-access/README.md
+++ b/publishing-documentation/authenticated-access/README.md
@@ -9,7 +9,7 @@ icon: key
Authenticated access allows you to publish your content while requiring authentication from any visitors who want to view it. When enabled, GitBook lets your authentication provider handle who has access to the content.
-
Add a sign in to your published documentation.
+
Add a sign in to your published documentation.
### Use cases
diff --git a/publishing-documentation/authenticated-access/setting-up-a-custom-backend.md b/publishing-documentation/authenticated-access/setting-up-a-custom-backend.md
index ef7b3050..fdeef2ab 100644
--- a/publishing-documentation/authenticated-access/setting-up-a-custom-backend.md
+++ b/publishing-documentation/authenticated-access/setting-up-a-custom-backend.md
@@ -111,7 +111,7 @@ For instance, if your login screen is located at `https://example.com/login`, yo
You can configure this fallback URL within your site’s audience settings under the "Authenticated access" tab.
-
Configure a fallback URL
+
Configure a fallback URL
When redirecting to the fallback URL, GitBook includes a `location` query parameter to the fallback URL that you can leverage in your handler to redirect the user to the original location of the user:
diff --git a/publishing-documentation/authenticated-access/setting-up-auth0.md b/publishing-documentation/authenticated-access/setting-up-auth0.md
index 663bfcdc..b36b5a3f 100644
--- a/publishing-documentation/authenticated-access/setting-up-auth0.md
+++ b/publishing-documentation/authenticated-access/setting-up-auth0.md
@@ -32,14 +32,14 @@ Configure Auth0 to work with adaptive content in GitBook.
### Create a new Auth0 application
-First, sign in to Auth0 platform and create a new application (or use an existing one) by clicking the Applications button in the left sidebar. If creating a new application, name it appropriately and choose "Regular Web Application" as the option. Click Create. You may need to be admin to follow along this guide.\
+First, sign in to Auth0 platform and create a new application (or use an existing one) by clicking the Applications button in the left sidebar. If creating a new application, name it appropriately and choose "Regular Web Application" as the option. Click Create. You may need to be admin to follow along this guide.
-
+
A quickstart panel will show up. Select Node.js (Express) option and then select "I want to integrate my app." You will see a screen prompting you to configure Auth0. It should look like the image below
-
+
Click on Save Settings And Continue.
@@ -51,19 +51,19 @@ We will need these to configure our Auth0 authenticated access Integration.
Please ensure at least one connection is enabled for your Auth0 application.
{% endhint %}
-
+
### Install and configure the Auth0 integration
Navigate to the Integrations tab in a site and locate the Auth0 integration or navigate directly to this [https://app.gitbook.com/integrations/VA-Auth0](https://app.gitbook.com/integrations/VA-Auth0).
-
+
Install the integration on your site.
Upon installation on site, you will see a modal asking you enter the Client ID, Auth0 Domain, and Client Secret.
-
+
For Client ID and Client Secret, paste in the value you copied from Auth0 Dashboard. For Auth0 Domain, enter the Domain copied from Auth0 (make sure to prefix it with `https://`) .
diff --git a/publishing-documentation/authenticated-access/setting-up-aws-cognito.md b/publishing-documentation/authenticated-access/setting-up-aws-cognito.md
index 6b732779..08e9b3ad 100644
--- a/publishing-documentation/authenticated-access/setting-up-aws-cognito.md
+++ b/publishing-documentation/authenticated-access/setting-up-aws-cognito.md
@@ -48,7 +48,7 @@ Click on the created app client and make a note of the Client ID and Client Secr
Navigate to integrations within the GitBook app, select authenticated access as the category, and install the AWS Cognito integration.
-
+
@@ -58,7 +58,7 @@ Open up the Cognito integration's configuration screen for the space you install
It should look like the following image:
-
+
For Client ID, Cognito Domain, and Client Secret, paste in the values you got from Cognito.
diff --git a/publishing-documentation/authenticated-access/setting-up-azure-ad.md b/publishing-documentation/authenticated-access/setting-up-azure-ad.md
index b2e1c8dc..eaf86221 100644
--- a/publishing-documentation/authenticated-access/setting-up-azure-ad.md
+++ b/publishing-documentation/authenticated-access/setting-up-azure-ad.md
@@ -50,19 +50,19 @@ Start by creating an app registration in your Microsoft Entra ID dashboard. This
6. Click **Register** to complete the app registration.\
-
Register an app for the GitBook VA integration.
+
Register an app for the GitBook VA integration.
7. You should then see your new app registration **Overview** screen. Copy and make note of the **Application (client) ID** and **Directory (tenant) ID**.\
-
Overview of the newly created app registration.
+
Overview of the newly created app registration.
8. Click on **Add a certificate or secret**. You should see the following **Certificates & Secrets** screen:\
-
Add a certificate or secret.
+
Add a certificate or secret.
9. Click on **+ New client secret**.
@@ -77,7 +77,7 @@ Once you've created the Azure AD app registration, the next step is to install t
2. Click on the **Integrations** button in the top right from your site’s settings.\
-
+
3. Click on **Authenticated Access** from the categories in the sidebar.
@@ -85,11 +85,11 @@ Once you've created the Azure AD app registration, the next step is to install t
5. Click **Install on this site**.\
-
+
6. After installing the integration on your site, you should see the integration's configuration screen:\
-
+
7. Enter the **Client ID**, **Tenant ID**, and **Client Secret** values you copied after [creating the Azure AD app registration](setting-up-azure-ad.md#id-1.-create-an-app-registration-in-azure-a-d) earlier, and click “Save”.
8. Copy the **URL** displayed **at the bottom of the dialog**.
9. Head back to the Azure AD app registration you created earlier in the Microsoft Entra ID dashboard.
@@ -97,11 +97,11 @@ Once you've created the Azure AD app registration, the next step is to install t
11. Click **+ Add a platform** and select **Web** card in the panel that opens.\
-
+
12. Paste the GitBook integration **URL** you copied earlier in the **Redirect URI** field, and click “Configure”\
-
+
13. Head back to **Azure integration** installation screen **in GitBook**.
@@ -111,7 +111,7 @@ Once you've created the Azure AD app registration, the next step is to install t
17. Click **Update audience**.\
-
+
18. Head to the site's overview screen and click **Publish** if the site is not already published.
\
diff --git a/publishing-documentation/authenticated-access/setting-up-oidc.md b/publishing-documentation/authenticated-access/setting-up-oidc.md
index 4b0e88c1..351b9eee 100644
--- a/publishing-documentation/authenticated-access/setting-up-oidc.md
+++ b/publishing-documentation/authenticated-access/setting-up-oidc.md
@@ -37,7 +37,7 @@ There are some things that you need to set up on your Identity Provider in order
You need to create a new app inside your Identity Provider. Its type should be "Web Application." In Google, you create these under "API and Services", "Credentials", and then under "OAuth 2.0 Client IDs."\
-
+
Click on Create Credentials, select OAuth Client ID, select Web Application as the type, name it appropriately, and under Authorized Redirect URIs, enter the Callback URL you got from GitBook.
@@ -47,7 +47,7 @@ Click Create. Make a note of the Client ID and Client Secret. We will need these
Navigate to integrations within the GitBook app, select authenticated access as the category, and install the OIDC integration. Install the OIDC integration on your chosen docs site.
-
+
Once you've installed it on your site, go to configuration and make a note of the Callback URL right above the Save button. We may need it to set up the Identity Provider.
@@ -55,7 +55,7 @@ Open up the OIDC integration's configuration screen for the space you installed
It should look like the following image
-
+
diff --git a/publishing-documentation/authenticated-access/setting-up-okta.md b/publishing-documentation/authenticated-access/setting-up-okta.md
index 366c6650..9a8f3170 100644
--- a/publishing-documentation/authenticated-access/setting-up-okta.md
+++ b/publishing-documentation/authenticated-access/setting-up-okta.md
@@ -34,17 +34,17 @@ Configure Okta to work with adaptive content in GitBook.
First, sign in to Okta platform (the admin version) and create a new app integration (or use an existing one) by clicking the Applications button in the left sidebar.
-
+
Click Create App Integration and select OIDC - OpenID Connect as the Sign-In method. And then select Web Application as the application type.
-
+
Name it appropriately and don't edit any other setting on that page. For assignments, choose the appropriate checkbox. Click Save.
On the next screen, copy Client ID and Client Secret. Copy the Okta Domain right below your email address by clicking the dropdown in the top right.
-
+
We will need these values to configure the Okta Integration.
@@ -52,13 +52,13 @@ We will need these values to configure the Okta Integration.
Navigate to the Integrations tab in the site you want to publish and locate the Okta integration or navigate directly to this [https://app.gitbook.com/integrations/VA-Okta](https://app.gitbook.com/o/d8f63b60-89ae-11e7-8574-5927d48c4877/s/zq8ynchcecIscc4uulgN/).
-
+
Install the integration on your site.
Upon installation on site, you will see a screen asking you enter the Client ID, Okta Domain, and Client Secret.
-
+
For Client ID, Okta Domain (remove `https://`prefix, if any) and Client Secret, paste in the value you copied from Okta Dashboard.
@@ -66,7 +66,7 @@ Click Save.
Copy the URL displayed in the modal and enter it as a Sign-In redirect URI in Okta (as shown in the below screenshot). Hit Save.
-
+
Now, in GitBook, close the integrations modal and click on the Manage site button. Navigate to **Audience**, select **Authenticated access**, and choose Okta as the backend. Then, click **Update audience**. Go to the site’s screen and click **Publish**.\
\
diff --git a/publishing-documentation/customization/README.md b/publishing-documentation/customization/README.md
index f8a6713b..f9d82aeb 100644
--- a/publishing-documentation/customization/README.md
+++ b/publishing-documentation/customization/README.md
@@ -11,7 +11,7 @@ You can customize the appearance of your published documentation, match the user
You can apply customizations to your entire docs site as a site-wide theme, or to individual variants and site sections.
-
GitBook's own documentation is an example of a customized docs site.
+
GitBook's own documentation is an example of a customized docs site.
### Customizing sites with multiple sections
@@ -22,12 +22,12 @@ Select the whole site or a specific site section using the drop-down menu at the
* **Site-wide settings** – These automatically apply to all linked spaces.
* **Section specific settings** – If you’re using site sections, you’re can set section specific customization that will override the default site-wise setting.
-
The customization panel in GitBook.
+
The customization panel in GitBook.
{% hint style="warning" %}
Changes you make to specific site sections will override the site-wide customization settings, even if you change the site-wide setting again later.
-You can reset customization overrides back to the site-wide default by clicking the **Reset** button next to the space selector.
+You can reset customization overrides back to the site-wide default by clicking the **Reset** button next to the space selector.
{% endhint %}
### What counts as ‘Advanced customization’?
diff --git a/publishing-documentation/customization/icons-colors-and-themes.md b/publishing-documentation/customization/icons-colors-and-themes.md
index 64e6d112..ac6c49f1 100644
--- a/publishing-documentation/customization/icons-colors-and-themes.md
+++ b/publishing-documentation/customization/icons-colors-and-themes.md
@@ -6,7 +6,7 @@ description: Customize icons, colors, themes and more.
### Title, icon and logo
-
+
**Title**
@@ -34,7 +34,7 @@ The icon setting lets you upload a small, 132×132 px image, which will appear _
Themes let you customize the color scheme of your published content for both light and dark mode. There are four themes to choose from. The colors of your site will be directly impacted by the **primary color** and **tint** that you choose. These two selections affect various parts of the interface and can completely change the look and feel of your site.
-
+
#### Clean
@@ -58,7 +58,7 @@ A trendsetting theme featuring a gradient background and splashes of color. The
### Colors
-
+
#### Primary color
@@ -86,7 +86,7 @@ _Note: to change the theme within the GitBook app, go to your Settings menu at t
### Site styles
-
+
**Font family** **(Premium & Ultimate)**
@@ -115,7 +115,7 @@ Choose between two link designs:
### Sidebar styles
-
+
**Background style**
diff --git a/publishing-documentation/customization/layout-and-structure.md b/publishing-documentation/customization/layout-and-structure.md
index e2cd2d06..ccf96bcf 100644
--- a/publishing-documentation/customization/layout-and-structure.md
+++ b/publishing-documentation/customization/layout-and-structure.md
@@ -6,7 +6,7 @@ description: Customize the layout and structure of your published documentation.
### Header
-
+
**Search bar**
@@ -30,7 +30,7 @@ Control the display of the “previous” and “next” buttons that appear at
### Footer (Premium & Ultimate)
-
+
**Logo**
diff --git a/publishing-documentation/insights.md b/publishing-documentation/insights.md
index a9861155..f4c487b0 100644
--- a/publishing-documentation/insights.md
+++ b/publishing-documentation/insights.md
@@ -13,7 +13,7 @@ You can see a top-level overview of your insights on the **Overview** tab of you
Click the **Insights** tab in the site header to find more detailed insights for your site.
-
The site insights dashboard.
+
The site insights dashboard.
### Filters & groups
diff --git a/publishing-documentation/publish-a-docs-site/README.md b/publishing-documentation/publish-a-docs-site/README.md
index 0034b6d5..5e9ff800 100644
--- a/publishing-documentation/publish-a-docs-site/README.md
+++ b/publishing-documentation/publish-a-docs-site/README.md
@@ -9,7 +9,7 @@ Once you’ve finished writing, editing, or importing your content, you can publ
The content on your site comes from [spaces](../../creating-content/content-structure/space.md) in your organization. When you create a new docs site, you can create a new space, or link an existing one.
-
GitBook's docs sites homepage.
+
GitBook's docs sites homepage.
### Create a docs site
diff --git a/publishing-documentation/site-redirects.md b/publishing-documentation/site-redirects.md
index 1cf94619..79fa821a 100644
--- a/publishing-documentation/site-redirects.md
+++ b/publishing-documentation/site-redirects.md
@@ -7,7 +7,7 @@ icon: diamond-turn-right
{% include "../.gitbook/includes/premium-and-ultimate-hint.md" %}
-
Site redirects are useful when migrating documentation or restructuring content to avoid broken links, which can impact SEO.
+
Site redirects are useful when migrating documentation or restructuring content to avoid broken links, which can impact SEO.
Redirects are commonly used when you are migrating your documentation from one provider to another — like when you just moved docs to GitBook. Broken links can impact SEO so we recommend setting up redirects where needed.
@@ -25,7 +25,7 @@ If you want to add another redirect to the same page, you can toggle the **Add a
### Editing redirects
-To edit a redirect, press the **Edit** icon next to it in the list. Update the redirect and hit **Save**.
+To edit a redirect, press the **Edit** icon next to it in the list. Update the redirect and hit **Save**.
To delete a redirect, press the **Delete redirect** button and confirm.
diff --git a/publishing-documentation/site-settings.md b/publishing-documentation/site-settings.md
index 1eff1787..35c14602 100644
--- a/publishing-documentation/site-settings.md
+++ b/publishing-documentation/site-settings.md
@@ -7,7 +7,7 @@ icon: gear
{% include "../.gitbook/includes/customization-premium-and-ultimate-hint.md" %}
-
Update the settings for your published documentation.
+
Update the settings for your published documentation.
### General
diff --git a/publishing-documentation/site-structure/README.md b/publishing-documentation/site-structure/README.md
index 6195c387..0981a60a 100644
--- a/publishing-documentation/site-structure/README.md
+++ b/publishing-documentation/site-structure/README.md
@@ -19,7 +19,7 @@ From your docs site’s dashboard, open the **Settings** tab in the site header,
Your site starts out with a single section with your site's name and a single variant with the space you linked during your site's set-up.
-
The structure of a published docs site.
+
The structure of a published docs site.
### Linking a space to your docs site
@@ -31,19 +31,19 @@ When you add a space — as a variant or a section — a name and slug will be g
### Changing sections or variants
-
Update a site section or variant.
+
Update a site section or variant.
-You can change the name and slug of each of sections and variants by clicking the **Edit** button in the table row of the item you’d like to edit. This will open a modal. Edit the field(s) you’d like to change, then click the **Save** button to save.
+You can change the name and slug of each of sections and variants by clicking the **Edit** button in the table row of the item you’d like to edit. This will open a modal. Edit the field(s) you’d like to change, then click the **Save** button to save.
{% hint style="info" %}
Changing a linked space's slug will change the space's canonical URL. GitBook will create an automatic redirect from the old URL to the new one. You can also [manually create redirects](../site-redirects.md).
{% endhint %}
-To replace a section or variant, first delete it by clicking its **Edit** button, then click the **Delete** button in the lower left of the modal. Once the item is deleted, click the **Add section** or **Add variant** button to add it again.
+To replace a section or variant, first delete it by clicking its **Edit** button, then click the **Delete** button in the lower left of the modal. Once the item is deleted, click the **Add section** or **Add variant** button to add it again.
### Reordering sections or variants
-Your site displays sections and variants in the order that they appear in your **Site structure** table. They can be reordered by grabbing the **Drag handle** and moving it up or down. The changed order will be reflected on your site immediately.
+Your site displays sections and variants in the order that they appear in your **Site structure** table. They can be reordered by grabbing the **Drag handle** and moving it up or down. The changed order will be reflected on your site immediately.
You can also use the keyboard to select and move content. Select a section or variant with the space bar, then use the arrow keys to move it up or down. Hit the space bar again to confirm the new position.
@@ -53,7 +53,7 @@ If you have multiple sections in your site, one section will be marked as **Defa
If you have multiple variants within a section, one variant will be marked as the default. Like sections, the default variant is shown when visitors arrive on your site, or when they visit a section. Other variants each have a slug that’s appended to the section’s URL.
-To set a space as default, click on the **Actions menu** in the space’s table row and then click **Set as default**.
+To set a space as default, click on the **Actions menu** in the space’s table row and then click **Set as default**.
{% hint style="info" %}
Setting a space as default removes its slug field, as it will be served from the section root instead. GitBooks redirects the space’s slug to the appropriate path, to ensure visitors keep seeing your content.
@@ -63,7 +63,7 @@ Setting a space as default removes its slug field, as it will be served from the
To remove the content of a space from a site, open the **Settings** tab from your docs site dashboard, then click **Structure** to find the content you want to remove.
-Open the **Actions menu** for the space you want to remove and choose **Remove**.
+Open the **Actions menu** for the space you want to remove and choose **Remove**.
{% hint style="success" %}
Removing a space from your site will remove it from the published site, but **will not delete the space or the content within it**.
diff --git a/publishing-documentation/site-structure/site-sections.md b/publishing-documentation/site-structure/site-sections.md
index 5096c469..a9df5cb3 100644
--- a/publishing-documentation/site-structure/site-sections.md
+++ b/publishing-documentation/site-structure/site-sections.md
@@ -8,7 +8,7 @@ description: >-
{% include "../../.gitbook/includes/ultimate-hint.md" %}
-
Example of a GitBook site with site sections
+
Example of a GitBook site with site sections
With site sections, you can centralize all your documentation and create a seamless experience for your users.
@@ -30,7 +30,7 @@ From your docs site’s dashboard, open the **Settings** tab in the site header,
To add a site section, click the **New section** button underneath the table and choose a space to link as a section. The new section is then added to the table and will be available to visitors as a tab at the top of your site.
-
Add structure to your docs with site sections.
+
Add structure to your docs with site sections.
### Create a site section group
@@ -40,7 +40,7 @@ To create a group, click the arrow next to the **New section** button and choose
### Editing a section
-You can change the name, icon and slug of each of your sections by tapping the **Edit** button in the table row of the section you’d like to edit. This will open a modal. Edit the field(s) you’d like to change, then click the **Save** button. You can also delete the variant by clicking the **Delete variant** button in the lower left.
+You can change the name, icon and slug of each of your sections by tapping the **Edit** button in the table row of the section you’d like to edit. This will open a modal. Edit the field(s) you’d like to change, then click the **Save** button. You can also delete the variant by clicking the **Delete variant** button in the lower left.
{% hint style="info" %}
Changing a section’s slug will change its canonical URL. GitBook will create an automatic redirect from the old URL to the new one. You can also [manually create redirects](../site-redirects.md).
@@ -50,7 +50,7 @@ Site sections within a group can also optionally display a description, which wi
### Reordering sections
-Your site displays sections in the order that they appear in your Site structure table. Sections can be reordered by grabbing the **Drag handle** and moving it up or down. All the spaces within that section will be moved with it. The changed order will be reflected on your site immediately.
+Your site displays sections in the order that they appear in your Site structure table. Sections can be reordered by grabbing the **Drag handle** and moving it up or down. All the spaces within that section will be moved with it. The changed order will be reflected on your site immediately.
You can also use the keyboard to select and move content: select a section with the space bar, then use the arrow keys to move it up or down. Hit the space bar again to confirm the new position.
@@ -58,15 +58,15 @@ You can also use the keyboard to select and move content: select a section with
If you have multiple sections in your site, one section will be marked as the default. This section is shown when visitors arrive on your site, and is served from your site’s root URL. Other sections each have a slug that is appended to the root URL.
-To set a section as default, click on the **Actions menu** in the section's table row and then click **Set as default**.
+To set a section as default, click on the **Actions menu** in the section's table row and then click **Set as default**.
### Remove a section
-To remove a section from a site, click the **Settings** button from your docs site dashboard, then click **Structure** to find the content you want to remove. Click the **Edit** button next to the section you want to remove, then click the **Delete** button in the lower left of the modal. This will remove the section, along with all the variants within it, from the published site. It will not delete the spaces itself, or the content within them.
+To remove a section from a site, click the **Settings** button from your docs site dashboard, then click **Structure** to find the content you want to remove. Click the **Edit** button next to the section you want to remove, then click the **Delete** button in the lower left of the modal. This will remove the section, along with all the variants within it, from the published site. It will not delete the spaces itself, or the content within them.
To remove a section from a site, open the **Settings** tab from your docs site dashboard, then click **Structure** to find the content you want to remove.
-Open the **Actions menu** for the space you want to remove and choose **Remove**.
+Open the **Actions menu** for the space you want to remove and choose **Remove**.
{% hint style="success" %}
Removing a section from your site will remove it — and all variants within it — from the published site, but **will not delete any of the spaces or the content within them**.
diff --git a/publishing-documentation/site-structure/variants.md b/publishing-documentation/site-structure/variants.md
index 513f35c0..dea52e3c 100644
--- a/publishing-documentation/site-structure/variants.md
+++ b/publishing-documentation/site-structure/variants.md
@@ -8,7 +8,7 @@ description: >-
You can publish multiple versions of the same documentation as part of a single docs site. These variants will be available to the end users via the space switcher in the top-left corner of the published site.
-
+
### Add multiple languages or versions
@@ -26,17 +26,17 @@ To add a variant, click the **Add variant** button in the section you'd like to
### Changing a variant
-You can change the name and slug of each of your variants by clicking the **Edit** button in the table row of the variant you’d like to edit. This will open a modal. Edit the field(s) you'd like to change, then click the **Save** button to save. You can also delete the variant by clicking the **Delete variant** button in the lower left.
+You can change the name and slug of each of your variants by clicking the **Edit** button in the table row of the variant you’d like to edit. This will open a modal. Edit the field(s) you'd like to change, then click the **Save** button to save. You can also delete the variant by clicking the **Delete variant** button in the lower left.
{% hint style="info" %}
Changing a linked space's slug will change the space's canonical URL. GitBook will create an automatic redirect from the old URL to the new one. You can also [manually create redirects](../site-redirects.md).
{% endhint %}
-To replace a variant’s linked space with a different space, first delete it by clicking its **Edit** button, then click the **Delete** button in the lower left of the modal. Once the variant is deleted, click the **Add variant** button to add the new space.
+To replace a variant’s linked space with a different space, first delete it by clicking its **Edit** button, then click the **Delete** button in the lower left of the modal. Once the variant is deleted, click the **Add variant** button to add the new space.
### Reordering variants
-Your site displays variants in the order that they appear in your **Site structure** table. Variants can be reordered by grabbing the **Drag handle** and moving it up or down. The changed order will be reflected on your site immediately.
+Your site displays variants in the order that they appear in your **Site structure** table. Variants can be reordered by grabbing the **Drag handle** and moving it up or down. The changed order will be reflected on your site immediately.
You can also use the keyboard to select and move content: select a section or variant with the space bar, then use the arrow keys to move it up or down. Hit the space bar again to confirm the new position.
@@ -44,7 +44,7 @@ You can also use the keyboard to select and move content: select a section or va
If you have multiple variants within a section, one variant will be marked as the default. This variant is shown when visitors arrive on your site (or when they visit a section). Other variants each have a slug that is appended to the site's URL.
-To set a variant as default, click on the **Actions menu** in the variant’s table row and then click **Set as default**.
+To set a variant as default, click on the **Actions menu** in the variant’s table row and then click **Set as default**.
{% hint style="info" %}
Setting a variant as default removes its slug field, as it will be served from the section root instead. GitBook will redirect the variant's slug to the appropriate path, to ensure visitors keep seeing your content.
@@ -54,7 +54,7 @@ Setting a variant as default removes its slug field, as it will be served from t
To remove a variant from a site, open the **Settings** tab from your docs site dashboard, then click **Structure** to find the content you want to remove.
-Open the **Actions menu** for the variant you want to remove and choose **Remove**.
+Open the **Actions menu** for the variant you want to remove and choose **Remove**.
{% hint style="success" %}
Removing a variant from your site will remove it from the published site, but **will not delete the space or the content within it**.
diff --git a/resources/gitbook-ui.md b/resources/gitbook-ui.md
index 1ec6be72..72b8ddb9 100644
--- a/resources/gitbook-ui.md
+++ b/resources/gitbook-ui.md
@@ -9,7 +9,7 @@ GitBook is split into different sections to make it easier to organize and manag
### Sidebar
-
The GitBook sidebar holds all of your documentation, as well as notifications, the search bar, snippets and more.
+
The GitBook sidebar holds all of your documentation, as well as notifications, the search bar, snippets and more.
The sidebar allows you to see and overview of your GitBook organization at a glance. The sidebar contains:
@@ -36,7 +36,7 @@ The sidebar allows you to see and overview of your GitBook organization at a gla
### Table of contents
-
The table of contents lists all the pages and links in your selected space.
+
The table of contents lists all the pages and links in your selected space.
By default, the table of contents shows a list of [pages, links, and groups](../creating-content/content-structure/page.md#organizing-your-content) that make up a space. You’ll find it to the right of the sidebar. It’s specific to the space you’re currently viewing.
@@ -48,7 +48,7 @@ From the **Pages** tab in the table of contents you can:
* Create [page groups](gitbook-ui.md#groups)
* Add [external links](gitbook-ui.md#external-links)
* [import external docs](../getting-started/import.md) like websites or Markdown files
-* Access [the Actions menu](gitbook-ui.md#the-actions-menu) for individual pages.
+* Access [the Actions menu](gitbook-ui.md#the-actions-menu) for individual pages.
In the **Reusable content** tab, you can:
@@ -63,11 +63,11 @@ In the **Files** tab, you can:
* Drag and drop more files into your space
* Manage individual files
-If you want to give more focus to the content of your page, you can temporarily hide the table of contents by hovering your cursor next to it and clicking the **Hide** button that appears. To make it appear again, hover your cursor near the edge of the page and click the **Show** button .
+If you want to give more focus to the content of your page, you can temporarily hide the table of contents by hovering your cursor next to it and clicking the **Hide** button that appears. To make it appear again, hover your cursor near the edge of the page and click the **Show** button .
### Space header
-
The space header sits at the top of the editor, and offers options that apply to the whole space.
+
The space header sits at the top of the editor, and offers options that apply to the whole space.
The space header contains information about the space you’re currently viewing. It lets you do things like publish and share your space, view the comments and history for the space, configure [GitHub or GitLab sync](../getting-started/git-sync/), and more.
@@ -85,7 +85,7 @@ The space header includes:
The name of the space that will appear in the sidebar, and your documentation if and when you choose to publish it.
* **The space’s breadcrumbs**\
A full, linear list of the collections or docs sites the space lives in.
-* **Actions menu** \
+* **Actions menu** \
Offers a list of actions for your space. Similar to [page actions](gitbook-ui.md#the-actions-menu), the available actions for a space will differ depending on the mode you’re currently in.
* **Editor view**\
This view is where you can make edits to your content using GitBook’s block-based editor.
@@ -120,7 +120,7 @@ The site header includes:
The name of the space that will appear in the sidebar, and your documentation if and when you choose to publish it.
* **The site’s breadcrumbs**\
A link back to the main Docs sites screen.
-* **Actions menu** \
+* **Actions menu** \
Offers a list of actions for your site. You can visit your site or copy its URL quickly from this menu
* **Overview**\
The site overview shows you essential information about your site including it’s URL, publish status, audience and content, as well as top-level insights.
@@ -152,14 +152,14 @@ At the top of each page you can set a **title**, add an optional **emoji**, and
Your page description can be a maximum of 200 characters long, and will act as the preview text for your page in search engines.
{% hint style="info" %}
-You can change the URL slug for a page by choosing **Page Actions** > **Rename**. Find out more about [Page Actions](gitbook-ui.md#page-options) below.
+You can change the URL slug for a page by choosing **Page Actions** > **Rename**. Find out more about [Page Actions](gitbook-ui.md#page-options) below.
{% endhint %}
### Page actions menu
-The page’s **Actions menu** allows you to do things like duplicate, rename or delete your page.
+The page’s **Actions menu** allows you to do things like duplicate, rename or delete your page.
-You can open the **Actions menu** using the icon that appears when hovering over your page in the sidebar, or from the icon next to the page title.
+You can open the **Actions menu** using the icon that appears when hovering over your page in the sidebar, or from the icon next to the page title.
{% hint style="info" %}
The type of actions available will depend on whether you’re in [live editing](../collaboration/live-edits.md) mode or a [change request](../collaboration/change-requests.md).
@@ -167,11 +167,11 @@ The type of actions available will depend on whether you’re in [live editing](
### Page options
-
The Page options side panel offers customization options for your documentation and navigation.
+
The Page options side panel offers customization options for your documentation and navigation.
With page options, you cam customize your documentation layout and navigation. You can only access page options if you’re in an editing mode.
-You can open the **Page options** side panel by opening the page’s **Action menu** and choosing **Options**, or by hovering over the main title of the page and clicking **Page options** when it appears.
+You can open the **Page options** side panel by opening the page’s **Action menu** and choosing **Options**, or by hovering over the main title of the page and clicking **Page options** when it appears.
{% hint style="info" %}
Certain changes, such as disabling the table of content, only apply to published documentation and may not be visible in the editor.
@@ -179,7 +179,7 @@ Certain changes, such as disabling the table of content, only apply to published
### Page outline
-
The page outline shows H1 and H2 headings, allowing you to quickly jump to a specific section on an individual page.
+
The page outline shows H1 and H2 headings, allowing you to quickly jump to a specific section on an individual page.
The **page outline** sits on the right-hand side of the editor, and makes it easy to jump directly to the section of the page you’re looking for.
diff --git a/snippets/snippets-beta.md b/snippets/snippets-beta.md
index 84d45571..8f6ea56f 100644
--- a/snippets/snippets-beta.md
+++ b/snippets/snippets-beta.md
@@ -20,7 +20,7 @@ In GitBook, you can capture unstructured information using [integrations](broken
GitBook will index all of your snippets alongside the rest of your content and can reference them when you or your team [searches for information](../creating-content/searching-your-content/). You can also merge snippets into existing docs or content to keep everything up to date.
-
The Snippets page holds all of your snippets in one place and makes it easy to connect integrations so you can add more.
+
The Snippets page holds all of your snippets in one place and makes it easy to connect integrations so you can add more.
### Product Demo
@@ -46,7 +46,7 @@ You can create a snippet manually from the **Snippets** page, by clicking the **
You can edit a snippet you’ve captured by clicking to open it from the **Snippets** page. This will open an editor view, where you can edit any information that might be wrong, or add additional context for things that might be missing.
-
You can edit a snippet directly in the editor by opening it.
+
You can edit a snippet directly in the editor by opening it.
icon at the bottom of the sidebar and then click on **\[organization name] settings** to get there.
+1. Go to the organization’s settings page. You can click on the settings 
.svg)
+
image
+This is an inline 
image
+This is an inline 
[GitBook Support](mailto:support@gitbook.com).
+If everything fails, please share the details with 
+
+
.svg)
.svg)
.svg)
.svg)
