env: line edits

src/technical/env/environments.md

@@ -2,7 +2,7 @@
 
 The bare minimum Wormhole environment is just a blockchain linked up to a Guardian node. There are quite a few ways of accomplishing this, and if you're just looking to get your feet wet, you should try whichever sounds easiest.
 
-However, as you get deeper into cross-chain development you'll likely find you have a growing number of components, dependencies, and teammates in the picture making your development environment more complex. Here are some of the considerations you should have in mind when choosing a development environment which will be well suited for your xDapp.
+However, as you get deeper into cross-chain development, you'll likely find yourself with a growing number of components, dependencies, and teammates in the picture making your development environment more complex. Here are some of the considerations you should have in mind when choosing a development environment which will be well suited for your xDapp.
 
 ### What components do I need now? What components will I need in the future?
 
@@ -10,9 +10,9 @@ However, as you get deeper into cross-chain development you'll likely find you h
 
 ### What are my dependencies?
 
-- If your smart contracts have no dependencies, it may be possible for you to develop in a vacuum. However, if you're working on a fledgling blockchain and trying to integrate with other applications which are also in development, you may have no choice but to work in testnet alongside other development teams.
+- If your smart contracts have no dependencies, it may be possible for you to develop in a vacuum.
 
-- Just because you have dependencies doesn't mean you automatically have to develop in testnet or mainnet. Often times it's relatively trivial to redeploy your dependencies in Tilt, or to use something like [Foundry](https://github.com/foundry-rs/foundry) to create a development version of an existing testnet or mainnet.
+- If your smart contracts does have dependencies, there are several options that range from deploying your dependencies in Tilt or use something like [Foundry](https://github.com/foundry-rs/foundry) to simulate an existing testnet or mainnet in your local devnet to working to working directly in testnet alongside other teams.
 
 ### How am I going to collaborate?
 

src/technical/env/testnet.md

@@ -2,7 +2,7 @@
 
 Wormhole testnet is spread across many of the most popular testnet blockchains.
 
-The primary reason to use Wormhole testnet is in order to simplify the management of your dependent contracts. This will vary from blockchain to blockchain.
+The primary reason to use Wormhole testnet is to simplify the management of your dependent contracts. This will vary from blockchain to blockchain.
 
 For example, some blockchain ecosystems have the standard that their contracts are closed-source, and there are no tools to fork mainnet. Other ecosystems, such as EVM, have tools like [foundry](https://github.com/foundry-rs/foundry), which allow you to hardfork the mainnet ecosystem into a local development node.
 

src/technical/env/tilt.md

@@ -4,9 +4,9 @@
 
 [Tilt](https://tilt.dev/) is part of the official Docker ecosystem. It's a tool which allows developers to easily configure a Kubernetes environment for development.
 
-However, in the context of Wormhole, the 'Tilt' usually refers to the development environment used by the [Wormhole Core Repository](https://github.com/wormhole-foundation/wormhole). This environment uses Tilt to stand up all the tools necessary to build across multiple blockchains. It has docker images for all the common items encountered during cross-chain developing, including:
+However, in the context of Wormhole, 'Tilt' usually refers to the development environment used by the [Wormhole Core Repository](https://github.com/wormhole-foundation/wormhole). This environment uses Tilt to stand up docker images for all the tools necessary to build across multiple blockchains, including:
 
-- All the supported blockchains / ecosystems of Wormhole
+- All the Wormhole supported blockchains / ecosystems
 - A Guardian Node
 - Relayers
 - Databases, Redis

src/technical/env/troubleshooting.md

@@ -2,7 +2,7 @@
 
 Tilt, Kubernetes, and Docker may be new tools for developers entering the Wormhole ecosystem. This section is meant to provide some additional support when setting up the Wormhole Tilt environment.
 
-## macOS Install
+# macOS Install
 
 ## Prerequisites
 
@@ -14,13 +14,13 @@ Having `homebrew` on your system makes the installation really straightforward.
 
 From there, all the other installs are one-liners.
 
-## Install Go
+### 1. Install Go
 
 ```sh
 brew install go
 ```
 
-## Install Docker
+### 2. Install Docker
 
 ```sh
 brew install docker
@@ -28,13 +28,13 @@ brew install docker
 
 After installation, go into Docker settings and switch ON `kubernetes`. Also configure Docker to have 4 CPUs and ~16GB of RAM.
 
-## Install Tilt
+### 3. Install Tilt
 
 ```sh
 brew install tilt
 ```
 
-## Clone Wormhole Repo and Start Tilt
+### 4. Clone Wormhole Repo and Start Tilt
 
 ```sh
 git clone --branch dev.v2 https://github.com/wormhole-foundation/wormhole.git
@@ -48,9 +48,9 @@ tilt up
 You'll be able to access the Tilt UI at
 `localhost:10350`
 
-## Linux & WSL Install
+# Linux & WSL Install
 
-### Setup Script
+## Script Setup
 
 If you're using a Debian distro, you should run the [dev-setup.sh](https://github.com/wormhole-foundation/wormhole/blob/dev.v2/scripts/dev-setup.sh) script. Even if you're not using Debian, this script still contains the main steps for setup.
 
@@ -71,11 +71,11 @@ Also, make absolutely sure that you set up Docker as a non-root user.
 
 [https://docs.docker.com/engine/install/ubuntu/#installation-methods](https://docs.docker.com/engine/install/ubuntu/#installation-methods)
 
-### 3. (Docker Desktop Install)
+### 3a. (Docker Desktop Install)
 
 Enable Kubernetes by going into Settings > Kubernetes
 
-### 3. (Non Docker Desktop)
+### 3b. (Non Docker Desktop)
 
 Install [`minikube`](https://minikube.sigs.k8s.io/docs/start/).