diff --git a/docs/guides/lint-asyncapi.md b/docs/guides/lint-asyncapi.md index 4f273fed..9de21681 100644 --- a/docs/guides/lint-asyncapi.md +++ b/docs/guides/lint-asyncapi.md @@ -99,13 +99,12 @@ opportunities to make sure that your AsyncAPI spec conforms with expectations (we'd also love to see what you're building, it helps us know how things are going!). -:::info Custom plugins - +{% admonition type="info" name="Custom plugins" %} For those users with advanced requirements and JavaScript skills, the [custom plugins](../custom-plugins/index.md) feature offers some extension points if you need them. -::: +{% /admonition %} ## Supported protocols diff --git a/docs/guides/migrate-from-swagger-cli.md b/docs/guides/migrate-from-swagger-cli.md index 24f131f9..60221ec9 100644 --- a/docs/guides/migrate-from-swagger-cli.md +++ b/docs/guides/migrate-from-swagger-cli.md @@ -46,14 +46,8 @@ redocly lint openapi.yml You can add more [built-in rules](../rules/built-in-rules.md) by adding them in the configuration file, and adjust the level of the messages by using `warn` rather than `error`. - - - - Learn more about [configuring Redocly CLI](../configuration/index.md) in the documentation. - - ## Bundle OpenAPI/Swagger into a single file While the OpenAPI (and earlier Swagger) standards were designed to use `$ref` reference syntax and re-use elements of API descriptions across mulitple files, not all tools support this. If there's a tool in your API lifecycle that needs a single file, you can still use mulitple files for the day-to-day work, and then "bundle" the API description into a single file for use by another tool.