diff --git a/Contributing.md b/Contributing.md
index 8cbdc20b..4bad8dfe 100644
--- a/Contributing.md
+++ b/Contributing.md
@@ -8,28 +8,33 @@ yarn
 npm -i
 ```
 
-## Before you begin
+## Setting Up Your Salesforce Development Environment
 
-### Check your development environment
+### Be aware of your development options
 
-This monorepo allows you to develop the app in either a scratch org or in a sandbox or Developer Edition org.
+Apex Rollup is a monorepo that contains both the base unlocked package's source code and the source code for various plugin packages. Not _all_ of the code is required to be deployed if you aren't looking to work on plugins, but because the "Apex Rollup - Nebula Logger" plugin relies on [Nebula Logger](https://github.com/jongpie/NebulaLogger/) being installed, you have some choices to make if you want to use the `Push Source To Default Org` and CLI equivalents in a Source Tracking-enabled development environment.
 
-#### For orgs with Source Tracking enabled
+You can either:
 
-Install the Nebula Logger version provided in the `sfdx-project.json`'s `packageAliases` attribute. Using the CLI, do it like this:
+1. Install the Nebula Logger version provided in the `sfdx-project.json`'s `packageAliases` attribute. Using the CLI, do it like this:
 
 ```bash
 sf package install -p <package version 04t> -w 30 -r
 ```
 
-#### For orgs that do not have Source Tracking enabled
+or:
 
-Deploy the contents of the `rollup` folder directly with:
+2. Deploy the unlocked package source directories:
 
 ```bash
 sf project deploy start --source-dir ./rollup
+sf project deploy start --source-dir ./extra-tests
 ```
 
+or:
+
+3. Comment out the "Apex Rollup - Nebula Logger" plugin within the `packageDirectories` list in `sfdx-project.json` - this will allow `Push Source...` commands to work. Just remember to uncomment that plugin prior to submitting anything to be reviewed!
+
 ### Make sure to assign permissions to your user
 
 The app is available to users that have the two permissions. For development purposes we recommend having at least the two main permission sets assigned to your user. Assign them with these commands:
@@ -39,20 +44,7 @@ sf org assign permset -n See_Rollup_App
 sf org assign permset -n See_Rollup_Button
 ```
 
-## Ensure all rollup files are installed
-
-Whether you are developing on a sandbox or a new scratch org, please be sure to also deploy the `extra-tests` directory:
-
-```bash
-sf project deploy start --source-dir ./extra-tests
-```
-
-I've included helper scripts to aid in programmatically testing only Apex Rollup's test classes when developing in a sandbox within the `package.json` file - one need only invoke the tests like such on the command line:
-
-- `yarn test`
-- or `npm run test`
-
-Within a scratch org, validating that all of the tests run is as simple as invoking `sfdx force:apex:test:run -w 10`.
+## Prior To Submitting A Change/Pull Request
 
 When submitting a pull request, please follow these guidelines:
 
@@ -60,6 +52,4 @@ When submitting a pull request, please follow these guidelines:
 - ensure your dependencies have been installed and that any/all file(s) changed have had prettier-apex run on them (usually as simple as enabling "Format On Save" in your editor's options); alternatively you can always format the document in Vs Code using `Shift + Ctrl + F` or `cmd + Shift + F` once you're done writing. Your mileage may vary as to the hotkey if you're using Illuminated Cloud or another text editor; you always have the option of invoking prettier on the command-line
 - ensure that tests have been run against a scratch org with multi-currency enabled (you can look at [`scripts/test.ps1`](https://github.com/jamessimone/apex-rollup/blob/main/scripts/test.ps1) to see how the scratch org is created and the currency ISO codes are loaded).
 - ensure that any change to production code comes with the addition of tests. It's possible that I will accept PRs where _only_ production-level code is changed, if an optimization is put in place -- but otherwise, try to write a failing test first!
-- if you are testing on a scratch org, `sfdx force:source:push` will fail due to the Rollup Nebula Logger Adapter plugin. You can either:
-  - temporarily comment out that plugin within the `packageDirectories` list in `sfdx-project.json`
-  - install whichever `04t...` version of Nebula Logger the plugin relies upon by looking at the dependency listed within `sfdx-project.json`'s `packageAliases` object
+