Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: fix inconsistent capitalization of "API". #5824

Merged
merged 1 commit into from
Dec 6, 2018
Merged

docs: fix inconsistent capitalization of "API". #5824

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/implement-api-bindings.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ handled for you by writes to the request body blocking.)

Like with everything else, IPFS aims to be flexible regarding the API transports.
Currently, the [go-ipfs](https://github.com/ipfs/go-ipfs) implementation supports
both an in-process API and an HTTP api. More can be added easily, by mapping the
both an in-process API and an HTTP API. More can be added easily, by mapping the
API functions over a transport. (This is similar to how gRPC is also _mapped on
top of transports_, like HTTP).

Expand Down