Skip to content

Commit bcc80ad

Browse files
Fix sentence case in titles and headings (#1443)
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: Devin Logan <[email protected]>
1 parent c084883 commit bcc80ad

File tree

16 files changed

+28
-28
lines changed

16 files changed

+28
-28
lines changed

fern/products/api-def/asyncapi-pages/automation.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Sync your AsyncAPI Specification
2+
title: Sync your AsyncAPI specification
33
subtitle: Automatically sync your AsyncAPI spec changes to keep SDKs and docs up to date
44
---
55

@@ -200,4 +200,4 @@ api:
200200
version: 0.8.8
201201
```
202202
203-
This ensures that any breaking changes to your AsyncAPI specification are detected and the appropriate team members are notified before the changes are propagated to your SDKs and documentation.
203+
This ensures that any breaking changes to your AsyncAPI specification are detected and the appropriate team members are notified before the changes are propagated to your SDKs and documentation.

fern/products/api-def/asyncapi-pages/extensions/parameter-names.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Parameter Names
2+
title: Parameter names
33
subtitle: Use `x-fern-parameter-name` to customize SDK parameter names for message properties
44
---
55

@@ -76,4 +76,4 @@ channels:
7676
type: string
7777
```
7878
79-
This ensures consistent naming conventions across your SDK while maintaining compatibility with your existing message formats.
79+
This ensures consistent naming conventions across your SDK while maintaining compatibility with your existing message formats.

fern/products/api-def/asyncapi-pages/overview.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: What is an AsyncAPI Specification?
2+
title: What is an AsyncAPI specification?
33
description: AsyncAPI is a standard for documenting event-driven APIs
44
---
55

@@ -174,4 +174,4 @@ fern/
174174
└─ asyncapi.yml
175175
```
176176
</Step>
177-
</Steps>
177+
</Steps>

fern/products/api-def/ferndef-pages/api-yml/global-configuration.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Global Configuration
2+
title: Global configuration
33
description: Specify global headers, path parameters or query parameters meant to be included on every request.
44
---
55

@@ -52,4 +52,4 @@ service:
5252
## Global query parameters
5353

5454
You cannot yet specify query parameters that are meant to be included on every request.
55-
If you'd like to see this feature, please upvote [this issue](https://github.com/fern-api/fern/issues/2930).
55+
If you'd like to see this feature, please upvote [this issue](https://github.com/fern-api/fern/issues/2930).

fern/products/api-def/ferndef-pages/endpoints/bytes.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Binary Data and Files
2+
title: Binary data and files
33
subtitle: Use the `bytes` type to handle binary data in your API
44
---
55

fern/products/api-def/ferndef-pages/endpoints/multipart.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Multipart File Upload
2+
title: Multipart file upload
33
description: Document endpoints with the `multiform` content type.
44
---
55

fern/products/api-def/ferndef-pages/endpoints/sse.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Server-Sent Events and Streaming APIs
2+
title: Server-sent events and streaming APIs
33
subtitle: Use the `response-stream` key to model streaming endpoints
44
---
55

@@ -97,4 +97,4 @@ types:
9797
ChatChunk:
9898
properties:
9999
text: string
100-
```
100+
```

fern/products/api-def/grpc-pages/automation.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Sync your gRPC Specification
2+
title: Sync your gRPC specification
33
subtitle: Automatically sync your Protocol Buffer changes to keep SDKs and docs up to date
44
---
55

@@ -469,4 +469,4 @@ if __name__ == "__main__":
469469
sync_from_grpc_reflection("localhost:50051", "proto/")
470470
```
471471
472-
This ensures that any changes to your gRPC services are automatically reflected in your SDKs and documentation, maintaining consistency across your entire API ecosystem.
472+
This ensures that any changes to your gRPC services are automatically reflected in your SDKs and documentation, maintaining consistency across your entire API ecosystem.

fern/products/api-def/grpc-pages/services/errors.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Error Handling
2+
title: Error handling
33
subtitle: Implement robust error handling with gRPC status codes and custom error details
44
---
55

@@ -523,4 +523,4 @@ message CreateUserResult {
523523
}
524524
```
525525

526-
Proper error handling in gRPC ensures robust, maintainable services that provide clear feedback to clients about what went wrong and how to fix it.
526+
Proper error handling in gRPC ensures robust, maintainable services that provide clear feedback to clients about what went wrong and how to fix it.

fern/products/api-def/openapi-pages/automation.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Sync your OpenAPI Specification
2+
title: Sync your OpenAPI specification
33
subtitle: Pull your latest OpenAPI Specification into your Fern Folder automatically.
44
---
55

@@ -59,4 +59,4 @@ This creates daily pull requests with any API spec updates. To change the freque
5959

6060
## Other use cases
6161

62-
If your OpenAPI spec lives in a different repository (rather than at a public URL), you can sync it to your Fern folder using explicit file mappings. See the [sync-openapi GitHub Action README](https://github.com/fern-api/sync-openapi) for this and other advanced configurations.
62+
If your OpenAPI spec lives in a different repository (rather than at a public URL), you can sync it to your Fern folder using explicit file mappings. See the [sync-openapi GitHub Action README](https://github.com/fern-api/sync-openapi) for this and other advanced configurations.

0 commit comments

Comments
 (0)