CyberCoveLLC/threshold
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix spelling errors found in the documentation (#1073)

Browse Source
This commit is contained in:
John Reese authored and GitHub committed 2021-04-08 12:14:36 -04:00
1 parent d3146992f1
commit c096157cf9
10 files changed
+11 -11
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

website/content/docs/api-clients/api.mdx
+2 -2
View File
@@ -7,7 +7,7 @@ description: |-
# API
Boundary's API is a a JSON-based HTTP API that adheres to a set of standards that are rigidly followed. At its core, it is a standards-compliant JSON API for both input and output.
Boundary's API is a JSON-based HTTP API that adheres to a set of standards that are rigidly followed. At its core, it is a standards-compliant JSON API for both input and output.
Before reading this page, it is useful to understand Boundary's [domain model](/docs/concepts/domain-model) to be aware of the terminology used here.
@@ -64,7 +64,7 @@ The following method conventions are used within Boundary's API:
### POST
`POST` is used for creating a resource or performing custom actions against a resoruce. When creating a resource, `POST` is used against a collection (`/roles`). When performing a custom action, `POST` is used against a particular resource (`/roles/r_1234567890:set-principals`).
`POST` is used for creating a resource or performing custom actions against a resource. When creating a resource, `POST` is used against a collection (`/roles`). When performing a custom action, `POST` is used against a particular resource (`/roles/r_1234567890:set-principals`).
### PATCH