docs: reuse code snippet to show configurable rule per api

Author: adamaltman

docs/@v1/guides/configure-rules.md

@@ -114,37 +114,11 @@ Not all APIs are made equal. Perhaps your newsletter signup microservice is held
 
 You can configure linting differently for multiple APIs in a Redocly configuration file. Here's an example with three APIs defined, and different rules applied for each:
 
-```yaml
-extends:
-  - recommended
-
-apis:
-  partnerApi@1:
-    root: partners.yaml
-    rules:
-      no-server-trailing-slash: off
-      operation-operationId: off
-
-  newsletter@3:
-    root: /absolute/path/to/folder/openapi.yaml
-    extends:
-      - minimal
-    rules:
-      no-server-trailing-slash: off
-
-  UserApi@1:
-    root: users.yaml
-    rules:
-      no-server-trailing-slash: off
-      operation-operationId: warn
-      assert/version-semver:
-        subject:
-          type: Info
-          property: version
-        assertions:
-          pattern: /1.[0-9]\.[0-9]/
-        message: API version must be in SemVer format, no major version release
-```
+{% code-snippet 
+  file="../../_code-snippets/per-api-rules-example.yaml"
+  language="yaml"
+  title="redocly.yaml"
+/%}
 
 There's a few things going on in the example, but let's look at each feature in turn:
 

docs/@v1/rules/configure-rules.md

@@ -53,6 +53,18 @@ apis:
 
 Each API picks up the settings that relate to it and gets linted accordingly.
 
+## Per-API configuration with configurable rules
+
+You can use configurable rules for individual APIs.
+In the following example, `UserApi@1` has a configurable rule defined.
+This rule applies only to `UserApi@1`.
+
+{% code-snippet 
+  file="../../_code-snippets/per-api-rules-example.yaml"
+  language="yaml"
+  title="redocly.yaml"
+/%}
+
 ## Resources
 
 - Learn more about [rules and rulesets](../rules.md).

docs/@v2/guides/configure-rules.md

@@ -123,37 +123,11 @@ Whatever the reason, per-API configuration can be useful in these situations.
 You can configure linting differently for multiple APIs in a Redocly configuration file.
 Here's an example with three APIs defined, and different rules applied for each:
 
-```yaml
-extends:
-  - recommended
-
-apis:
-  partnerApi@1:
-    root: partners.yaml
-    rules:
-      no-server-trailing-slash: off
-      operation-operationId: off
-
-  newsletter@3:
-    root: /absolute/path/to/folder/openapi.yaml
-    extends:
-      - minimal
-    rules:
-      no-server-trailing-slash: off
-
-  UserApi@1:
-    root: users.yaml
-    rules:
-      no-server-trailing-slash: off
-      operation-operationId: warn
-      rule/version-semver:
-        subject:
-          type: Info
-          property: version
-        assertions:
-          pattern: /1.[0-9]\.[0-9]/
-        message: API version must be in SemVer format, no major version release
-```
+{% code-snippet 
+  file="../../_code-snippets/per-api-rules-example.yaml"
+  language="yaml"
+  title="redocly.yaml"
+/%}
 
 There's a few things going on in the example, but let's look at each feature in turn:
 

docs/@v2/rules/configure-rules.md

@@ -53,6 +53,18 @@ apis:
 
 Each API picks up the settings that relate to it and gets linted accordingly.
 
+## Per-API configuration with configurable rules
+
+You can use configurable rules for individual APIs.
+In the following example, `UserApi@1` has a configurable rule defined.
+This rule applies only to `UserApi@1`.
+
+{% code-snippet 
+  file="../../_code-snippets/per-api-rules-example.yaml"
+  language="yaml"
+  title="redocly.yaml"
+/%}
+
 ## Resources
 
 - Learn more about [rules and rulesets](../rules.md).

docs/_code-snippets/per-api-rules-example.yaml

@@ -0,0 +1,29 @@
+extends:
+  - recommended
+
+apis:
+  partnerApi@1:
+    root: partners.yaml
+    rules:
+      no-server-trailing-slash: off
+      operation-operationId: off
+
+  newsletter@3:
+    root: /absolute/path/to/folder/openapi.yaml
+    extends:
+      - minimal
+    rules:
+      no-server-trailing-slash: off
+
+  UserApi@1:
+    root: users.yaml
+    rules:
+      no-server-trailing-slash: off
+      operation-operationId: warn
+      assert/version-semver:
+        subject:
+          type: Info
+          property: version
+        assertions:
+          pattern: /1.[0-9]\.[0-9]/
+        message: API version must be in SemVer format, no major version release