From a81683d3f9da3c8c76934598f13fbac040f1c830 Mon Sep 17 00:00:00 2001 From: Mat Kelly Date: Thu, 6 Dec 2018 12:13:41 -0500 Subject: [PATCH] docs: fix inconsistent capitalization of "API". --- docs/implement-api-bindings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/implement-api-bindings.md b/docs/implement-api-bindings.md index 50172cc0112..364f3265e2e 100644 --- a/docs/implement-api-bindings.md +++ b/docs/implement-api-bindings.md @@ -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).