update rest of parachains section

3-parachains/3-interact.md

@@ -7,21 +7,8 @@ parachains and interact with them.
 
 We've already connected the Apps UI to the relay chain node. Now we can also connect to the
 parachain collator. Open another instance of Apps in a new browser window, and connect it to the
-appropriate endpoint. If you have followed these instructions so far, you can connect to Alice's
-node at https://polkadot.js.org/apps/#/?rpc=ws://localhost:9977
-
-## Adding Custom Types
-
-The Collator has introduced some custom data types that the front end does not know about. In order
-to properly encode transactions, we must tell the front end about these types. Enter the following
-json in the `Settings` -> `Developer` tab.
-
-```json
-{
-  "Address": "AccountId",
-  "LookupSource": "AccountId"
-}
-```
+appropriate endpoint. If you have followed these instructions so far, you can connect to the
+parachain node at https://polkadot.js.org/apps/#/?rpc=ws://localhost:9855
 
 ## Submit Transactions
 

3-parachains/4-more-nodes.md

@@ -11,21 +11,23 @@ we used to start the first collator, but again we need to avoid conflicting port
 
 ```bash
 parachain-collator \
+  --collator \
   --tmp
-  --bootnodes <Your first collator> \
-  --ws-port <Your chosen websocket port> \
-  --port <Your chosen libp2p port> \
   --parachain-id <Your ID> \
-  --validator \
+  --port <Your chosen libp2p port> \
+  --ws-port <Your chosen websocket port> \
+  --bootnodes <Your first collator> \
   -- \ # Any flags after this -- go to the embedded polkadot node
-  --chain spec.json \
+  --chain <relay chain spec json> \
+  --port <Your chosen libp2p port> \
+  --ws-port <Your chosen websocket port> \
   --bootnodes <Alice, Bob, and other relay chain collators>
 ```
 
 ## Full Nodes
 
 It is also possible to start non-collating full nodes in the parachain. For these options, simply
-leave out the `--validator` flag.
+leave out the `--collator` flag.
 
 ```bash
 parachain-collator \