Skip to content

Commit c68c6f7

Browse files
authored
Update overrides.mdx
Add a link to Fern extensions in the overides page
1 parent a804573 commit c68c6f7

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

fern/products/api-def/pages/overrides.mdx

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Use an overrides file to customize your API definition without modifying the ori
99
* You need different configurations for SDKs versus documentation
1010

1111
<Note>
12-
While you can also embed Fern extensions directly in your API specification, using overrides files is the recommended approach as it keeps your original spec clean and separates concerns.
12+
While you can also embed [Fern extensions](https://buildwithfern.com/learn/api-definitions/openapi/extensions/overview) directly in your API specification, using overrides files is the recommended approach as it keeps your original spec clean and separates concerns.
1313
</Note>
1414

1515
## Implement overrides
@@ -31,8 +31,7 @@ fern/
3131
<Note> The format of the overrides file is independent from the spec. For example, even if your OpenAPI spec is in JSON format, you can write the overrides in yaml. </Note>
3232

3333
</Step>
34-
<Step title="Add customizations">
35-
34+
<Step title="Customize your spec with Fern extensions">
3635
```yml title="overrides.yml" {4-5}
3736
paths:
3837
/users:
@@ -172,4 +171,4 @@ Learn more about the customizations you can make for each definition:
172171
</Card>
173172
<Card title="gRPC" href="/api-definitions/grpc/extensions/overview">
174173
</Card>
175-
</CardGroup>
174+
</CardGroup>

0 commit comments

Comments
 (0)