GitBook: [#63] Minor tweaks to developers section

Author: asaj

developers/advanced/connection-client.md

@@ -24,7 +24,7 @@ Using an `AbacusConnectionManager` allows applications to migrate to a new Abacu
 
 ## Abacus Connection Client
 
-``[`AbacusConnectionClient`](https://github.com/abacus-network/abacus-monorepo/blob/main/solidity/app/contracts/AbacusConnectionClient.sol) is a simple mix-in contract that application developers can inherit from in order to connect to Abacus.
+[`AbacusConnectionClient`](https://github.com/abacus-network/abacus-monorepo/blob/main/solidity/app/contracts/AbacusConnectionClient.sol) is a simple mix-in contract that application developers can inherit from in order to connect to Abacus.
 
 This contract maintains a pointer to an `AbacusConnectionManager`. Application developers can choose to deploy their own connection manager, or point to an existing contract that's managed by an entity they trust.
 

developers/advanced/message-encoding.md

@@ -4,13 +4,13 @@ description: Recommended approaches for encoding and decoding messages
 
 # Message encoding
 
-Abacus cross-chain messages are encoded as raw byte arrays. In order to send and receive messages, developers should implement functions for encoding and decoding cross-chain messages. 
+Abacus interchain messages are encoded as raw byte arrays. In order to send and receive messages, developers should implement functions for encoding and decoding interchain messages. 
 
-In this section, we describe two recommended approaches and their trade-offs.
+In this section, we describe two recommended approaches and their tradeoffs.
 
 ### General
 
-In most cases, we expect that developers are sending cross-chain messages in order to call a function on a contract on remote chain. For that, it is necessary to encode and decode raw bytes to an equivalent of a function call with arguments.
+In most cases, we expect that developers are sending interchain messages in order to call a function on a contract on remote chain. For that, it is necessary to encode and decode raw bytes to an equivalent of a function call with arguments.
 
 #### ABI Encoding
 

developers/advanced/router-pattern.md

@@ -6,7 +6,7 @@ description: A pattern for building interchain applications
 
 While patterns and best practices will evolve over time, the Router pattern has emerged as a useful model for building interchain applications.
 
-The Router pattern allows developers to write application logic once while deploying it to many networks. Developers can leverage this pattern by inheriting from the [`Router.sol` mix-in contract](https://github.com/abacus-network/abacus-monorepo/blob/main/solidity/app/contracts/Router.sol), and implementing functions that send and receive messages to and from remote chains.
+It allows developers to write application logic once while deploying it to many networks. Developers can leverage this pattern by inheriting from the [`Router.sol` mix-in contract](https://github.com/abacus-network/abacus-monorepo/blob/main/solidity/app/contracts/Router.sol), and implementing functions that send and receive messages to and from remote chains.
 
 Developers then deploy their contracts on each chain that they would like their application to support. Each contract must be made aware of their counterparts on all remote chains so that they can authenticate the messages that they send between each other.
 

developers/environments/README.md

@@ -2,7 +2,7 @@
 
 Throughout the Abacus Code bases exist the concept of environments to facilitate the development and testing of changes, both of the Abacus core platform as well as applications building on top of Abacus. Environments also encode the set of domains/chains that are supported. This page outlines the purpose of each environment and how developers should think about them.
 
-### Environment: \`test\`
+### Environment: "test"
 
 The `test` environment is meant for local development. Application developers can use the `@abacus-network/hardhat` plugin's `TestAbacusDeploy` object to deploy a mocked Abacus core platform. By calling `processMessages()`, developers can simulate the processing of messages across domains without having to run any of the Agents.
 

developers/environments/interaction-api.md

@@ -17,7 +17,7 @@ yarn add @abacus-network/sdk
 The `AbacusApp` abstraction is a mapping that resolves a network namespace to a collection of [ethers Contract](https://docs.ethers.io/v5/api/contract/contract/#Contract) instances on that network. A default implementation of this collection called [`AbacusContracts`](https://github.com/abacus-network/abacus-monorepo/blob/main/typescript/sdk/src/contracts.ts#L37) is provided which should satisfy most conceivable designs. This implementation ensures your contracts collections are attached to the appropriate network providers.
 
 {% hint style="info" %}
-Please see the [Examples section](../examples/) for a demonstration of how to leverage the `AbacusApp` abstraction`.`
+Please see the [Examples section](../examples/) for a demonstration of how to leverage the`AbacusApp` abstraction.
 {% endhint %}
 
 ### Interact

developers/environments/multiprovider.md

@@ -4,7 +4,7 @@ description: Manage node providers for Abacus supported networks in one plac
 
 # MultiProvider
 
- `MultiProvider` is a network utility used throughout the Abacus Application SDK. In essence, it is a mapping that resolves a network namespace to a configured node provider.
+`MultiProvider` is a network utility used throughout the Abacus Application SDK. In essence, it is a mapping that resolves a network namespace to a configured node provider.
 
 ### Configuration
 
@@ -13,11 +13,11 @@ It has a simple interface for configuring target networks that are supported by
 ```typescript
 const ethereum = {
     provider: new UrlJsonRpcProvider('http://localhost:8545/')
-}
+};
 const polygon = {
     provider: new UrlJsonRpcProvider('https://rpc-mainnet.matic.network'),
     confirmations: 10, // wait 10 blocks for finality
-}
+};
 const multiProvider = new MultiProvider({ ethereum, polygon });
 ```
 
@@ -40,8 +40,8 @@ import { ethers } from 'hardhat';
 const [signer] = await ethers.getSigners();
 const testMultiProvider = new MultiProvider({
     test1: { signer },
-    test2: { signer }
-    test3: { signer }
+    test2: { signer },
+    test3: { signer },
 });
 ```
 

developers/examples/README.md

@@ -1,2 +1,13 @@
-# Example apps
+# Examples
 
+{% content-ref url="ping-pong.md" %}
+[ping-pong.md](ping-pong.md)
+{% endcontent-ref %}
+
+{% content-ref url="erc20-token.md" %}
+[erc20-token.md](erc20-token.md)
+{% endcontent-ref %}
+
+{% content-ref url="controller.md" %}
+[controller.md](controller.md)
+{% endcontent-ref %}