From ea64795903c5808e64cfd8626f36e21869ab210c Mon Sep 17 00:00:00 2001 From: "Daniel X. Pape" Date: Wed, 8 Aug 2018 19:02:06 -0700 Subject: [PATCH] minor command name fix --- 04_4__Interlude_Using_Curl.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/04_4__Interlude_Using_Curl.md b/04_4__Interlude_Using_Curl.md index b3a0a3d..5ced3b6 100644 --- a/04_4__Interlude_Using_Curl.md +++ b/04_4__Interlude_Using_Curl.md @@ -14,7 +14,7 @@ In order to use `curl` with `bitcoind`, you must know three things: the standard ### Know Your Format -The `bitcoin-cli` commands are all linked to RPC commands in `bitcoind`. That makes the transition from using `bitcoin-cli` to using `curl` very simple. In fact, if you look at any of the help pages for `bitcoin-cli`, you'll see that they list not only the `bitcoin-cli` commands, but also parallel `curl` commands. For example, here is `bitcoin-cli getinfo help`: +The `bitcoin-cli` commands are all linked to RPC commands in `bitcoind`. That makes the transition from using `bitcoin-cli` to using `curl` very simple. In fact, if you look at any of the help pages for `bitcoin-cli`, you'll see that they list not only the `bitcoin-cli` commands, but also parallel `curl` commands. For example, here is `bitcoin-cli help getmininginfo`: ``` $ bitcoin-cli help getmininginfo getmininginfo