Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion credits.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@

[Narration](/assistant/narration) costs 50 credits when Mintlify successfully generates audio for a page. The first reader to listen triggers generation on demand. After generation finishes, Mintlify caches the audio and timing data, so subsequent plays by any reader consume no additional credits.

When you change a page's published narratable content, the next listener generates an updated recording for another 50 credits. Failed generations cost nothing. If multiple readers start narration before the first generation finishes and is cached, each request may generate audio and consume 50 credits.

Check warning on line 53 in credits.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

credits.mdx#L53

In general, use active voice instead of passive voice ('is cached').

### Automation updates

Expand All @@ -74,7 +74,7 @@

Credits are available on the Pro and Enterprise plans.

The Starter plan does not include AI features, and you cannot purchase credits on it. To use the assistant, agent, autopilot, or narration, upgrade to Pro or Enterprise.
The Starter plan does not include AI features, and you cannot purchase credits on it. To use the assistant, agent, Autopilot, or narration, upgrade to Pro or Enterprise.

<Note>
Customers on legacy credit plans keep their existing credit packs and pricing. The add-ons below apply to the Pro plan.
Expand Down
6 changes: 3 additions & 3 deletions deploy/azure-repos.mdx
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "Azure Repos"
description: "Connect an Azure Repos repository to Mintlify with Microsoft Entra ID for automatic deployments, pull request previews, web editor publishing, and Autopilot."
description: "Connect an Azure Repos repository to Mintlify with Microsoft Entra ID for automatic deployments, pull request previews, editor publishing, and Autopilot."
keywords: ["Azure DevOps", "Microsoft Entra ID", "service hooks", "automated deployments"]
---

Expand All @@ -10,7 +10,7 @@

Mintlify connects to Azure Repos through Microsoft Entra ID. You sign in with your Microsoft account so Mintlify can verify which organizations, projects, and repositories you can access. Mintlify then uses the Mintlify app in your Entra tenant to read your repository, create service hooks, deploy every change pushed to your deploy branch, and create preview deployments for pull requests.

Mintlify supports Azure DevOps Services organizations on `dev.azure.com`, including organizations that still use `*.visualstudio.com` URLs, that are connected to Microsoft Entra ID. Mintlify does not support Azure DevOps Server.

Check warning on line 13 in deploy/azure-repos.mdx

View check run for this annotation

Mintlify / Mintlify Validation (mintlify) - vale-spellcheck

deploy/azure-repos.mdx#L13

In general, use active voice instead of passive voice ('are connected').

## Requirements

Expand Down Expand Up @@ -58,7 +58,7 @@
1. Click **Connect**.
2. Confirm the change.

Mintlify verifies that your Microsoft account can manage the repository and that the deploy branch exists. Mintlify then registers the service hooks that keep your site and the web editor in sync and starts your first deployment.
Mintlify verifies that your Microsoft account can manage the repository and that the deploy branch exists. Mintlify then registers the service hooks that keep your site and the editor in sync and starts your first deployment.
</Step>
</Steps>

Expand All @@ -79,7 +79,7 @@

## Edit in the web editor

You can edit Azure Repos content in the [web editor](/editor). When you publish, Mintlify pushes a branch to Azure Repos and opens a pull request against your deploy branch.
You can edit Azure Repos content in the [editor](/editor). When you publish, Mintlify pushes a branch to Azure Repos and opens a pull request against your deploy branch.

- Branches that you push to Azure Repos sync into the editor.
- Changes to pull requests in Azure Repos sync into the matching editor branch.
Expand Down
Loading