From 9f0c149ded6d9a80c70f9904a0748005b1070ce4 Mon Sep 17 00:00:00 2001
From: Michael Bahr <1830132+bahrmichael@users.noreply.github.com>
Date: Wed, 4 Dec 2024 16:24:55 +0100
Subject: [PATCH] fix: grammar

---
 docs/batch-changes/faq.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/batch-changes/faq.mdx b/docs/batch-changes/faq.mdx
index 4fb8c3177..4058755cb 100644
--- a/docs/batch-changes/faq.mdx
+++ b/docs/batch-changes/faq.mdx
@@ -18,7 +18,7 @@ However, if the user deletion is permanent (using the "Delete forever" option),
 ## Are there any limitations with the Batch Changes feature?
 
 - **Code hosts**: Batch Changes currently support **GitHub**, **GitLab** and **Bitbucket Server and Bitbucket Data Center** repositories. If you want to use Batch Changes on other code hosts, [let us know](https://about.sourcegraph.com/contact).
-- **Server-side execution**: Batch change steps are run locally (in the [Sourcegraph CLI](https://github.com/sourcegraph/src-cli)) or [server-side](/batch-changes/server-side) `Beta`. For this reason, the APIs for creating and updating a batch change require you to upload all of the changeset specs (which are produced by executing the batch spec locally). Also, see [how scalable Batch Changes](/batch-changes/faq#how-scalable-are-batch-changes-how-many-changesets-can-i-create).
+- **Server-side execution**: Batch change steps are run locally (in the [Sourcegraph CLI](https://github.com/sourcegraph/src-cli)) or [server-side](/batch-changes/server-side) `Beta`. For this reason, the APIs for creating and updating a batch change require you to upload all of the changeset specs (which are produced by executing the batch spec locally). Also, see [how scalable Batch Changes are](/batch-changes/faq#how-scalable-are-batch-changes-how-many-changesets-can-i-create).
 - **Multi-user access**: It is yet to be possible for multiple users to edit the same batch change that was created under an organization.
 - It is yet to be possible to reuse a branch in a repository across multiple batch changes.
 - The only type of user credential supported by Sourcegraph right now is a [personal access token](/batch-changes/configuring-credentials), either per user, or via a global service account. Further credential types may be supported in the future.