Skip to content

Commit d9b0822

Browse files
committed
line edit
1 parent b4b9d20 commit d9b0822

File tree

2 files changed

+5
-8
lines changed

2 files changed

+5
-8
lines changed

articles/api-center/enable-managed-api-analysis-linting.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,7 @@ ms.custom:
1515
This article explains how to enable API analysis in [Azure API Center](overview.md) without having to manage it yourself (preview). API analysis offers linting capabilities to analyze API definitions in your organization's API center. Linting ensures your API definitions adhere to organizational style rules, generating both individual and summary reports. Use API analysis to identify and correct common errors and inconsistencies in your API definitions.
1616

1717
> [!IMPORTANT]
18-
> Managed API analysis in API Center sets up a linting engine and necessary dependencies automatically. You can also enable linting and analysis [manually](enable-api-analysis-linting.md) with a custom Azure function. **Disable any function used for manual linting before enabling managed linting.**
19-
20-
> [!NOTE]
21-
> Managed API analysis in API Center sets up a linting engine and necessary dependencies automatically. You can also enable linting and analysis [manually](enable-api-analysis-linting.md) with a custom Azure function. **Disable any function used for manual linting before enabling managed linting.**
18+
> Managed API analysis in API Center sets up a linting engine and necessary dependencies automatically. You can also enable linting and analysis [manually](enable-api-analysis-linting.md) using a custom Azure function. **Disable any function used for manual linting before enabling managed API analysis.**
2219
2320

2421
In this scenario:
@@ -33,9 +30,9 @@ In this scenario:
3330
* Currently, only OpenAPI specification documents in JSON or YAML format are analyzed.
3431
* By default, you enable analysis with the [`spectral:oas` ruleset](https://docs.stoplight.io/docs/spectral/4dec24461f3af-open-api-rules). To learn more about the built-in rules, see the [Spectral GitHub repo](https://github.com/stoplightio/spectral/blob/develop/docs/reference/openapi-rules.md).
3532
* Currently, you configure a single ruleset, and it's applied to all OpenAPI definitions in your API center.
36-
* Azure API Center applies the following limits for analysis and linting:
37-
* API definitions linted per 4 hours (Standard tier): 100
38-
* API definitions linted per 4 hours (Free tier): 10
33+
* hTe following are limits for maximum number of API definitions linted per 4 hours:
34+
* Free tier: 10
35+
* Standard tier: 100
3936

4037
## Prerequisites
4138

articles/api-center/includes/api-center-service-limits.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ ms.custom: Include file
2323
| Maximum number of custom metadata properties per entity<sup>3</sup> | 10 | 20 |
2424
| Maximum number of child properties in custom metadata property of type "object" | 10 |10 |
2525
| Maximum requests per minute (data plane) | 3,000 | 6,000 |
26-
| API definitions linted per 4 hours | 10 | 100 |
26+
| Maximum number of API definitions [linted](../enable-managed-api-analysis-linting.md) per 4 hours | 10 | 100 |
2727

2828
<sup>1</sup> To increase a limit in the Standard plan, contact [support](https://azure.microsoft.com/support/options/).<br/>
2929
<sup>2</sup> In the Free plan, use of full service features including API analysis and access through the data plane API is limited to 5 APIs.<br/>

0 commit comments

Comments
 (0)