diff options
| author | Giovanni HoSang <giovanni.hosang@gmail.com> | 2018-04-04 21:25:34 +0800 |
|---|---|---|
| committer | Felix Lange <fjl@users.noreply.github.com> | 2018-04-04 21:25:34 +0800 |
| commit | 1e248f3a6e14f3bfc9ebe1b315c4194300220f68 (patch) | |
| tree | 97d5f3fe8e0847b6f44b390694de8f3a25caf697 | |
| parent | 6ab9f0a19fbf548a78d08a526f522f41d8175a4e (diff) | |
| download | dexon-1e248f3a6e14f3bfc9ebe1b315c4194300220f68.tar.gz dexon-1e248f3a6e14f3bfc9ebe1b315c4194300220f68.tar.zst dexon-1e248f3a6e14f3bfc9ebe1b315c4194300220f68.zip | |
README: change 'built in' to 'built-in'
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -142,7 +142,7 @@ Do not forget `--rpcaddr 0.0.0.0`, if you want to access RPC from other containe ### Programatically interfacing Geth nodes As a developer, sooner rather than later you'll want to start interacting with Geth and the Ethereum -network via your own programs and not manually through the console. To aid this, Geth has built in +network via your own programs and not manually through the console. To aid this, Geth has built-in support for a JSON-RPC based APIs ([standard APIs](https://github.com/ethereum/wiki/wiki/JSON-RPC) and [Geth specific APIs](https://github.com/ethereum/go-ethereum/wiki/Management-APIs)). These can be exposed via HTTP, WebSockets and IPC (unix sockets on unix based platforms, and named pipes on Windows). |