fix: ✏️ Edit text for better consistency

This commit is contained in:
Jesse Wierzbinski 2024-08-18 00:59:39 +02:00
parent 94f437f539
commit 1f864b89c8
No known key found for this signature in database
7 changed files with 14 additions and 18 deletions

View file

@ -47,13 +47,13 @@ Accept: application/jrd+json
}
```
## Server Discovery
## Instance Discovery
Server metadata can be accessed by making a `GET` request to the server's Versia metadata endpoint, which is located at `/.well-known/versia`.
Instaance metadata can be accessed by making a `GET` request to the instance's Versia metadata endpoint, which is located at `/.well-known/versia`.
### Example
To discover the metadata of the server `versia.social`, an instance would make a `GET` request to `https://versia.social/.well-known/versia`.
To discover the metadata of the instance `versia.social`, an instance would make a `GET` request to `https://versia.social/.well-known/versia`.
This endpoint will return an [InstanceMetadata](/entities/instance-metadata) entity.

View file

@ -6,7 +6,7 @@ export const metadata = {
# Validation
Implementations **MUST** strictly validate all incoming data to ensure that it is well-formed and adheres to the Versia Protocol. If a request is invalid, the server **MUST** return a `400 Bad Request` HTTP status code.
Implementations **MUST** strictly validate all incoming data to ensure that it is well-formed and adheres to the Versia Protocol. If a request is invalid, the instance **MUST** return a `400 Bad Request` HTTP status code.
<Note>
Remember that while *your* implementation may disallow or restrict some user input, other implementations may not. You **should not** apply those restrictions to data coming from other instances.