Align docs with pricing page: fix plan references and rename snippets (#5620)

fern-api[bot] · devin-ai-integration[bot] · bot_apk · web-flow · commit ce7b85103aec · 2026-05-26T11:39:43.000-04:00
Co-authored-by: Devin AI &lt;158243242+devin-ai-integration[bot]@users.noreply.github.com&gt;
Co-authored-by: bot_apk &lt;apk@cognition.ai&gt;
diff --git a/fern/products/api-def/asyncapi/auth.mdx b/fern/products/api-def/asyncapi/auth.mdx
@@ -142,7 +142,7 @@ components:
 
 ## OAuth2 security scheme
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 OAuth2 authentication is supported for AsyncAPI specifications:
 
diff --git a/fern/products/api-def/asyncapi/extensions/audiences.mdx b/fern/products/api-def/asyncapi/extensions/audiences.mdx
@@ -5,7 +5,7 @@ subtitle: Use `x-fern-audiences` to filter to relevant operations, channels and
 ---
 
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 Audiences are a useful tool for segmenting your event-driven API for different consumers. Common examples of audiences include `public`
 and `beta`.
diff --git a/fern/products/api-def/ferndef/audiences.mdx b/fern/products/api-def/ferndef/audiences.mdx
@@ -7,7 +7,7 @@ noindex: true
 <Markdown src="/products/api-def/snippets/ferndef-support.mdx" />
 
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 Audiences are a useful tool for segmenting your API for different consumers. You can configure your Fern Docs to publish documentation specific to an `Audience`. You can use [audiences in your OpenAPI Specification](/learn/api-definitions/openapi/extensions/audiences), too. 
 
diff --git a/fern/products/api-def/ferndef/auth.mdx b/fern/products/api-def/ferndef/auth.mdx
@@ -182,7 +182,7 @@ client = new Client({
 
 ## OAuth client credentials
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 If your API uses OAuth, you can specify an oauth scheme in `api.yml` and define a token retrieval endpoint in a separate `auth.yml` file ([example](https://github.com/fern-api/fern/blob/3137938b70e058f3691ddef34d5c1cc29acc4b80/test-definitions/fern/apis/oauth-client-credentials/definition/api.yml)). 
 
diff --git a/fern/products/api-def/ferndef/endpoints/sse.mdx b/fern/products/api-def/ferndef/endpoints/sse.mdx
@@ -7,7 +7,7 @@ noindex: true
 <Markdown src="/products/api-def/snippets/ferndef-support.mdx" />
 
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 Specifying `response-stream` on an endpoints allows you to represent endpoint responses that are streaming. 
 
diff --git a/fern/products/api-def/openapi/endpoints/sse.mdx b/fern/products/api-def/openapi/endpoints/sse.mdx
@@ -40,7 +40,7 @@ components:
 
 ## Server-sent events 
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 If your API returns server-sent-events (SSE), with the `data` and `event` keys as seen below
 
diff --git a/fern/products/api-def/openapi/extensions/audiences.mdx b/fern/products/api-def/openapi/extensions/audiences.mdx
@@ -5,7 +5,7 @@ subtitle: Learn how to use x-fern-audiences to filter OpenAPI endpoints, schemas
 ---
 
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 Fern provides two ways to filter which API elements appear in your SDKs and API Reference docs:
 
diff --git a/fern/products/api-def/openapi/extensions/idempotency-headers.mdx b/fern/products/api-def/openapi/extensions/idempotency-headers.mdx
@@ -5,7 +5,7 @@ description: Configure idempotency for safe request retries using x-fern-idempot
 ---
 
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 Fern supports idempotency configuration through two extensions that work together: `x-fern-idempotency-headers` configures the idempotency headers your API uses, and `x-fern-idempotent` marks individual endpoints as idempotent. When configured, Fern's generated SDKs allow users to specify idempotency headers for safe request retries.
 
diff --git a/fern/products/api-def/openapi/extensions/pagination.mdx b/fern/products/api-def/openapi/extensions/pagination.mdx
@@ -5,7 +5,7 @@ description: Configure auto-pagination for list endpoints using the x-fern-pagin
 ---
 
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 The `x-fern-pagination` extension configures auto-pagination for list endpoints in your OpenAPI specification. [SDK](/learn/sdks/deep-dives/auto-pagination) and [CLI](/learn/cli-generator/get-started/openapi-extensions#pagination) users get automatic pagination without managing page tokens manually.
 
diff --git a/fern/products/api-def/openrpc/overview.mdx b/fern/products/api-def/openrpc/overview.mdx
@@ -4,8 +4,6 @@ description: Learn how to use OpenRPC specifications with Fern to document JSON-
 ---
 
 
-<Markdown src="/snippets/enterprise-plan.mdx"/>
-
 The OpenRPC Specification is a framework used by developers to document JSON-RPC APIs. The specification 
 is written in JSON or YAML and contains all of your methods, parameters, schemas, and server configurations. 
 Fern is compatible with OpenRPC specification [v1.3.2](https://spec.open-rpc.org/) and [v1.2.6](https://github.com/open-rpc/spec/releases/tag/1.2.6).
diff --git a/fern/products/docs/pages/navigation/versions.mdx b/fern/products/docs/pages/navigation/versions.mdx
@@ -4,9 +4,7 @@ subtitle: Add a dropdown version selector for multiple doc versions
 ---
 
 
-<Warning>
-  Versioning is available on [all plans](https://buildwithfern.com/pricing#Docs): up to 3 versions on Hobby, 10 versions on Team, or unlimited on Enterprise. Contact support@buildwithfern.com for more information.
-</Warning>
+<Markdown src="/snippets/team-plan.mdx"/>
 
 Each version of your docs can contain its own distinct tabs, sections, pages, and API references. Versions can also share content.
 
diff --git a/fern/products/sdks/deep-dives/configure-auto-pagination.mdx b/fern/products/sdks/deep-dives/configure-auto-pagination.mdx
@@ -4,7 +4,7 @@ description: Paginate through API responses with offset, cursor, URI, and path-b
 ---
 
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 Fern's auto-pagination supports offset, cursor, URI, and path-based
 pagination schemes, providing SDK users with simple iterators to loop through all
diff --git a/fern/products/sdks/deep-dives/configure-idempotency.mdx b/fern/products/sdks/deep-dives/configure-idempotency.mdx
@@ -4,7 +4,7 @@ description: Configure idempotency headers for SDKs that support retrying reques
 ---
 
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 For endpoints you've configured as idempotent, Fern's SDKs allow users to
 specify idempotency headers for safe request retries. Typically the headers include `Idempotency-Key`,
diff --git a/fern/products/sdks/deep-dives/filter-your-endpoints-audiences.mdx b/fern/products/sdks/deep-dives/filter-your-endpoints-audiences.mdx
@@ -4,7 +4,7 @@ description: Learn how to filter API endpoints using audiences in Fern SDKs. Gen
 ---
 
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 Use audiences to generate tailored SDKs for different groups of API consumers, such as internal teams, beta testers, or customers. 
 
diff --git a/fern/products/sdks/deep-dives/retries-with-backoff.mdx b/fern/products/sdks/deep-dives/retries-with-backoff.mdx
@@ -4,7 +4,7 @@ description: Learn how to configure automatic retries with exponential backoff i
 ---
 
 
-<Markdown src="/snippets/pro-plan.mdx" />
+<Markdown src="/snippets/enterprise-plan.mdx" />
 
 Fern SDKs will automatically retry failed requests with exponential backoff. A request will be retried as
 long as the request is deemed retryable and the number of retry attempts has
diff --git a/fern/products/sdks/deep-dives/testing.mdx b/fern/products/sdks/deep-dives/testing.mdx
@@ -8,7 +8,7 @@ Fern provides comprehensive testing for your SDKs through generated and handwrit
 
 ## Generated tests
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 Fern auto-generates tests that must pass before SDK release. Fern generates a GitHub workflow in each SDK repository that runs unit tests and any enabled mock server tests on every pull request, commit, and release.
 
diff --git a/fern/products/sdks/generators/java/configuration.mdx b/fern/products/sdks/generators/java/configuration.mdx
@@ -35,7 +35,7 @@ When enabled, generates `OptionalNullable<T>` types for merge patch request fiel
 
 <ParamField path="custom-dependencies" type="List<string>" required={false} toc={true}>
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 Example:
 
diff --git a/fern/products/sdks/generators/java/custom-code.mdx b/fern/products/sdks/generators/java/custom-code.mdx
@@ -290,7 +290,7 @@ protected void setAdditional(ClientOptions.Builder builder) {
 
 ## Adding custom dependencies
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 To add packages that your custom code requires, update your `generators.yml`.
 
diff --git a/fern/products/sdks/generators/python/configuration.mdx b/fern/products/sdks/generators/python/configuration.mdx
@@ -79,7 +79,7 @@ Customize the name of the generated environment class/enum. By default, the envi
 
 <ParamField path="extra_dependencies" type="object" default="{}" required={false} toc={true}>
 
-  <Markdown src="/snippets/pro-plan.mdx"/>
+  <Markdown src="/snippets/enterprise-plan.mdx"/>
 
   If you want to add custom dependencies to your generated SDK, you can specify them using this configuration. For example, to add a dependency on boto3, your config would look like:
   ```yaml
@@ -91,7 +91,7 @@ Customize the name of the generated environment class/enum. By default, the envi
 
 <ParamField path="extra_dev_dependencies" type="object" default="{}" required={false} toc={true}>
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 Specify additional development dependencies to include in the generated SDK's setup configuration. These are dependencies used for development and testing but not required by end users.
 </ParamField>
diff --git a/fern/products/sdks/generators/python/custom-code.mdx b/fern/products/sdks/generators/python/custom-code.mdx
@@ -118,7 +118,7 @@ To get started adding custom code:
 
 ## Adding custom dependencies
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 To add packages that your custom code requires, update your `generators.yml`.
 
diff --git a/fern/products/sdks/generators/ruby/configuration.mdx b/fern/products/sdks/generators/ruby/configuration.mdx
@@ -51,13 +51,13 @@ When enabled, generates [mock server (wire) tests](/sdks/deep-dives/testing#mock
 </ParamField>
 
 <ParamField path="extraDependencies" type="object" required={false} toc={true}>
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 Specify additional dependencies to include in the generated SDK's gemspec. This is useful when you need to add custom gems that your SDK depends on.
 </ParamField>
 
 <ParamField path="extraDevDependencies" type="object" required={false} toc={true}>
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 Specify additional development dependencies to include in the generated SDK's Gemfile. These are dependencies used for development and testing but not required by end users.
 </ParamField>
@@ -97,7 +97,7 @@ When enabled, the generated SDK omits the `X-Fern-Language`, `X-Fern-SDK-Name`,
 </ParamField>
 
 <ParamField path="requirePaths" type="array of strings" required={false} toc={true}>
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 Paths to files that will be auto-loaded when the gem is required. This is useful for including custom integrations or extensions that should be loaded automatically.
 
diff --git a/fern/products/sdks/generators/ruby/custom-code.mdx b/fern/products/sdks/generators/ruby/custom-code.mdx
@@ -99,7 +99,7 @@ To get started adding custom code:
 
 ## Adding custom dependencies
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 To add gems that your custom code requires, update your `generators.yml`.
 
diff --git a/fern/products/sdks/generators/typescript/configuration.mdx b/fern/products/sdks/generators/typescript/configuration.mdx
@@ -86,7 +86,7 @@ const bar: MyRootType.Foo.Bar = {};
 
 <ParamField path="extraDependencies" type="object" default="{}" toc={true}>
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
   Specify extra dependencies in the generated `package.json`. This is useful
 when you add custom code to your SDK that requires additional dependencies.
@@ -102,7 +102,7 @@ config:
 
 <ParamField path="extraDevDependencies" type="object" default="{}" toc={true}>
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
   Specify extra dev dependencies in the generated `package.json`. 
 
diff --git a/fern/products/sdks/generators/typescript/custom-code.mdx b/fern/products/sdks/generators/typescript/custom-code.mdx
@@ -135,7 +135,7 @@ The export key (e.g., `"./helper"`) determines the import path your users will u
 
 ## Custom dependencies
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 To add packages that your custom code requires, use the [`extraDependencies`](/sdks/generators/typescript/configuration#extraDependencies) and [`extraDevDependencies`](/sdks/generators/typescript/configuration#extraDevDependencies) options in your `generators.yml`.
 
diff --git a/fern/snippets/pro-plan.mdx b/fern/snippets/pro-plan.mdx
diff --git a/fern/snippets/team-or-enterprise-plan.mdx b/fern/snippets/team-or-enterprise-plan.mdx
@@ -0,0 +1,3 @@
+<Warning title="Team and Enterprise feature">
+    This feature is available only for the [Team and Enterprise plans](https://buildwithfern.com/pricing). To get started, reach out to support@buildwithfern.com.
+</Warning>
diff --git a/fern/snippets/team-or-pro-plan.mdx b/fern/snippets/team-or-pro-plan.mdx
diff --git a/fern/translations/zh/products/api-def/asyncapi/auth.mdx b/fern/translations/zh/products/api-def/asyncapi/auth.mdx
@@ -137,7 +137,7 @@ components:
 
 ## OAuth2 安全方案
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 AsyncAPI 规范支持 OAuth2 身份验证：
 
diff --git a/fern/translations/zh/products/api-def/asyncapi/extensions/audiences.mdx b/fern/translations/zh/products/api-def/asyncapi/extensions/audiences.mdx
@@ -6,7 +6,7 @@ sidebar-title: 使用受众筛选 API
 ---
 
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 受众是对事件驱动 API 进行分段以服务不同消费者的有用工具。常见的受众示例包括 `public` 和 `beta`。
 
diff --git a/fern/translations/zh/products/api-def/ferndef/audiences.mdx b/fern/translations/zh/products/api-def/ferndef/audiences.mdx
@@ -4,7 +4,7 @@ subtitle: 在 Fern 定义中使用受众来为不同的 API 消费者群体进
 noindex: true
 ---
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 受众是一个用于为不同消费者分段 API 的有用工具。您可以配置 Fern Docs 来发布特定于某个`受众`的文档。您也可以[在 OpenAPI 规范中使用受众](/learn/api-definitions/openapi/extensions/audiences)。
 
diff --git a/fern/translations/zh/products/api-def/ferndef/auth.mdx b/fern/translations/zh/products/api-def/ferndef/auth.mdx
@@ -173,7 +173,7 @@ client = new Client({
 
 ## OAuth 客户端凭据
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 如果您的 API 使用 OAuth，您可以在 `api.yml` 中指定 oauth 方案，并在单独的 `auth.yml` 文件中定义令牌检索端点（[示例](https://github.com/fern-api/fern/blob/3137938b70e058f3691ddef34d5c1cc29acc4b80/test-definitions/fern/apis/oauth-client-credentials/definition/api.yml)）。
 
diff --git a/fern/translations/zh/products/api-def/ferndef/endpoints/sse.mdx b/fern/translations/zh/products/api-def/ferndef/endpoints/sse.mdx
@@ -4,7 +4,7 @@ subtitle: 使用 `response-stream` 键来建模流式端点
 noindex: true
 ---
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 在端点上指定 `response-stream` 允许您表示流式响应的端点。
 
diff --git a/fern/translations/zh/products/api-def/openapi/endpoints/sse.mdx b/fern/translations/zh/products/api-def/openapi/endpoints/sse.mdx
@@ -41,7 +41,7 @@ components:
 
 ## 服务器发送事件
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 如果您的 API 返回服务器发送事件 (SSE)，包含 `data` 和 `event` 键，如下所示
 
diff --git a/fern/translations/zh/products/api-def/openapi/extensions/audiences.mdx b/fern/translations/zh/products/api-def/openapi/extensions/audiences.mdx
@@ -6,7 +6,7 @@ sidebar-title: 使用受众筛选 API
 ---
 
 
-<Markdown src="/snippets/team-or-pro-plan.mdx"/>
+<Markdown src="/snippets/team-or-enterprise-plan.mdx"/>
 
 Fern 提供两种方式来筛选哪些 API 元素会出现在您的 SDK 和 API 参考文档中：
 
diff --git a/fern/translations/zh/products/api-def/openapi/extensions/idempotency-headers.mdx b/fern/translations/zh/products/api-def/openapi/extensions/idempotency-headers.mdx
@@ -6,7 +6,7 @@ sidebar-title: 幂等性
 ---
 
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 Fern 通过两个协同工作的扩展支持幂等性配置：`x-fern-idempotency-headers` 配置您的 API 使用的幂等性头部，`x-fern-idempotent` 将单个端点标记为幂等的。配置后，Fern 生成的 SDK 允许用户指定幂等性头部以进行安全的请求重试。
 
diff --git a/fern/translations/zh/products/api-def/openapi/extensions/pagination.mdx b/fern/translations/zh/products/api-def/openapi/extensions/pagination.mdx
@@ -5,7 +5,7 @@ description: 使用 x-fern-pagination 扩展为列表端点配置自动分页
 ---
 
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 `x-fern-pagination` 扩展为 OpenAPI 规范中的列表端点配置自动分页。[SDK](/learn/sdks/deep-dives/auto-pagination) 和 [CLI](/learn/cli-generator/get-started/openapi-extensions#pagination) 用户无需手动管理页面令牌即可获得自动分页功能。
 
diff --git a/fern/translations/zh/products/api-def/openrpc/overview.mdx b/fern/translations/zh/products/api-def/openrpc/overview.mdx
@@ -5,8 +5,6 @@ sidebar-title: 什么是 OpenRPC 规范？
 ---
 
 
-<Markdown src="/snippets/enterprise-plan.mdx"/>
-
 OpenRPC 规范是开发人员用来文档化 JSON-RPC API 的框架。该规范使用 JSON 或 YAML 编写，包含您的所有方法、参数、模式和服务器配置。Fern 兼容 OpenRPC 规范 [v1.3.2](https://spec.open-rpc.org/) 和 [v1.2.6](https://github.com/open-rpc/spec/releases/tag/1.2.6)。
 
 以下是 OpenRPC 文件的示例：
diff --git a/fern/translations/zh/products/docs/pages/navigation/versions.mdx b/fern/translations/zh/products/docs/pages/navigation/versions.mdx
@@ -5,9 +5,7 @@ sidebar-title: 版本
 ---
 
 
-<Warning>
-  版本管理在[所有方案](https://buildwithfern.com/pricing#Docs)中均可使用：Hobby 最多 3 个版本，Team 最多 10 个版本，Enterprise 版本数量不限。如需更多信息，请联系 support@buildwithfern.com。
-</Warning>
+<Markdown src="/snippets/team-plan.mdx"/>
 
 您的文档的每个版本都可以包含自己独特的选项卡、章节、页面和 API 参考。版本之间也可以共享内容。
 
diff --git a/fern/translations/zh/products/sdks/deep-dives/configure-auto-pagination.mdx b/fern/translations/zh/products/sdks/deep-dives/configure-auto-pagination.mdx
@@ -4,7 +4,7 @@ description: 通过偏移量、游标、URI 和路径分页方式对 API 响应
 ---
 
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 Fern 的自动分页支持偏移量、游标、URI 和基于路径的分页方案，为 SDK 用户提供简单的迭代器来循环遍历所有结果，而不需要手动管理分页复杂性。
 
diff --git a/fern/translations/zh/products/sdks/deep-dives/configure-idempotency.mdx b/fern/translations/zh/products/sdks/deep-dives/configure-idempotency.mdx
@@ -4,7 +4,7 @@ description: 为支持重试请求的 SDK 配置幂等性请求头
 ---
 
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 对于您已配置为幂等的端点，Fern 的 SDK 允许用户为安全的请求重试指定幂等性请求头。通常这些请求头包括 `Idempotency-Key`，但您也可以指定其他请求头。
 
diff --git a/fern/translations/zh/products/sdks/deep-dives/filter-your-endpoints-audiences.mdx b/fern/translations/zh/products/sdks/deep-dives/filter-your-endpoints-audiences.mdx
@@ -4,7 +4,7 @@ description: 了解如何在 Fern SDK 中使用受众来过滤 API 端点。为
 ---
 
 
-<Markdown src="/snippets/pro-plan.mdx"/>
+<Markdown src="/snippets/enterprise-plan.mdx"/>
 
 使用受众为不同的 API 消费者群体（如内部团队、Beta 测试者或客户）生成定制的 SDK。
 
diff --git a/fern/translations/zh/products/sdks/deep-dives/retries-with-backoff.mdx b/fern/translations/zh/products/sdks/deep-dives/retries-with-backoff.mdx
diff --git a/fern/translations/zh/products/sdks/deep-dives/testing.mdx b/fern/translations/zh/products/sdks/deep-dives/testing.mdx
diff --git a/fern/translations/zh/products/sdks/generators/java/configuration.mdx b/fern/translations/zh/products/sdks/generators/java/configuration.mdx
diff --git a/fern/translations/zh/products/sdks/generators/java/custom-code.mdx b/fern/translations/zh/products/sdks/generators/java/custom-code.mdx
diff --git a/fern/translations/zh/products/sdks/generators/python/configuration.mdx b/fern/translations/zh/products/sdks/generators/python/configuration.mdx
diff --git a/fern/translations/zh/products/sdks/generators/python/custom-code.mdx b/fern/translations/zh/products/sdks/generators/python/custom-code.mdx
diff --git a/fern/translations/zh/products/sdks/generators/ruby/configuration.mdx b/fern/translations/zh/products/sdks/generators/ruby/configuration.mdx
diff --git a/fern/translations/zh/products/sdks/generators/ruby/custom-code.mdx b/fern/translations/zh/products/sdks/generators/ruby/custom-code.mdx
diff --git a/fern/translations/zh/products/sdks/generators/typescript/configuration.mdx b/fern/translations/zh/products/sdks/generators/typescript/configuration.mdx
diff --git a/fern/translations/zh/products/sdks/generators/typescript/custom-code.mdx b/fern/translations/zh/products/sdks/generators/typescript/custom-code.mdx
diff --git a/fern/translations/zh/snippets/pro-plan.mdx b/fern/translations/zh/snippets/pro-plan.mdx
diff --git a/fern/translations/zh/snippets/team-or-enterprise-plan.mdx b/fern/translations/zh/snippets/team-or-enterprise-plan.mdx
diff --git a/fern/translations/zh/snippets/team-or-pro-plan.mdx b/fern/translations/zh/snippets/team-or-pro-plan.mdx
