Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 3eb40af

Browse files
bkoelmanmaurei
andauthored
Update docs/getting-started/faq.md
Co-authored-by: Maurits Moeys <maurits.moeys@gmail.com>
1 parent febe396 commit 3eb40af

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎docs/getting-started/faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ This is useful if you want to add a few RPC-style endpoints or provide binary fi
106106
A middle-ground approach is to add custom action methods to existing JSON:API controllers.
107107
While you can route them as you like, they must return JSON:API resources.
108108
And on error, a JSON:API error response is produced.
109-
This is useful if you want to stay in the JSON:API-compliant world, but need to expose something on-standard, for example: `GET /users/me`.
109+
This is useful if you want to stay in the JSON:API-compliant world, but need to expose something non-standard, for example: `GET /users/me`.
110110

111111
#### How do I optimize for high scalability and prevent denial of service?
112112
Fortunately, JsonApiDotNetCore [scales pretty well](https://github.com/json-api-dotnet/PerformanceReports) under high load and/or large database tables.

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /