@@ -8,6 +8,8 @@ There are a total of eleven layer 2 actions, each corresponding to a familiar
88[layer 1 action](/docs/azimuth/ecliptic): `%transfer-point`, `%spawn`,
99`%configure-keys`, `%escape`, `%cancel-escape`, `%adopt`, `%reject`, `%detach`,
1010`%set-management-proxy`, `%set-spawn-proxy`, and `%set-transfer-proxy`.
11+Descriptions of what these actions do may be found by searching for them at
12+[Azimuth.eth](/docs/azimuth/azimuth-eth).
1113
1214Once a ship moves to layer 2, the owner will still utilize the same private keys
1315they used before the transfer to perform Azimuth actions. This includes the ownership
@@ -20,9 +22,8 @@ transferring ownership to layer 2.
2022
2123In order to move your ship from layer 1 to layer 2, transfer ownership of your
2224ship to the address `0x1111111111111111111111111111111111111111`. The easiest
23−way to accomplish this is using [Bridge](/docs/glossary/bridge), but Urbit-native CLI tools to accomplish this are available as
24−well (link). The Azimuth smart contracts interpret any ship at this address as
25−being on Layer 2.
25+way to accomplish this is using [Bridge](/docs/glossary/bridge). The Azimuth
26+smart contracts interpret any ship at this address as being on layer 2.
2627
2728### Dominion
2829