clarity update

Author: Kelly Tran

developer-guide/07-Plugins/03-plugin-as-python-package.md

@@ -340,6 +340,15 @@ include <PLUGIN_NAME>/LEADER_ONLY
 
 For an example, see the [logs2slack](https://github.com/Pioreactor/pioreactor-logs2slack) plugin's repository.
 
+## Install package from source
+
+It isn't enough to just `pip install` your package, as this will only add the script to the pioreactor system, not any extra configs you may have added. 
+If you want to install the whole package from source you can simply run:
+
+```
+pio plugins install <PLUGIN_NAME> --source <PLUGIN_FOLDER>
+```
+
 ## Create a Python package on PyPI
 
 Create an account on [https://pypi.org/](https://pypi.org/). Make sure to verify your email.

user-guide/01-getting-started/02-software-set-up.mdx

@@ -20,15 +20,15 @@ Before you get started, you'll need to have the following:
 
 1.  A Raspberry Pi (our list of recommended Raspberry Pis is [here](/user-guide/common-questions#what-raspberry-pi-hardware-can-i-use-i-see-raspberry-pi-1-2-3-4-a-b--zero---its-confusing))
 2.  A blank microSD card (our recommended microSD cards is [here](/user-guide/common-questions#what-microsd-cards-do-you-recommend))
-3.  A suitable power supply for the Raspberry Pi (our recommended power supply units are [here](/user-guide/common-questions#what-power-supply-unit-do-i-need))
+3.  A suitable power supply for the Raspberry Pi (our recommended power supply units are [here](/user-guide/common-questions#what-power-supply-unit-do-i-need)). You don't need to plug power in yet.
 4.  A computer with internet access and ability to read & write to a microSD card
 
 :::
 
-### Setting up your Raspberry Pi
+### Setting up your Raspberry Pi's SD Card
 
 
-We'll start your blank microSD card.
+We'll start with your blank microSD card.
 
 1. Download the [Pioreactor leader and worker image file](https://github.com/pioreactor/custopizer/releases/latest/download/pioreactor_leader_worker.zip). Leave it as a zip file - no need to unzip it.
 

user-guide/03-Extending your Pioreactor/06a-using-community-plugins.mdx

@@ -48,7 +48,7 @@ You can uninstall plugins from the same page, too. These will remove the action
  2. To get this .whl file onto a Pioreactor, use either `scp`, WinSCP, or FileZilla. Note: if you upload the .whl file to your leader Pioreactor first, you can distribute the .whl file to all your workers with `pios cp <location of .whl file>`
  3. Once the .whl file is on the Pioreactor, use the following to install the plugin:
     ```
-    pio plugin install <name-of-plugin> --source <location of .whl file>
+    pio plugins install <name-of-plugin> --source <location of .whl file>
     ```
     For example:
     ```
@@ -57,4 +57,4 @@ You can uninstall plugins from the same page, too. These will remove the action
 
 ## Alternative: putting Python files in the the `plugins` folder
 
-An alternative way to install a plugin is to place a Python file in the `/home/pioreactor/.pioreactor/plugins` directory on the Raspberry Pi. This is good for one-off scripts or plugins you are demoing or testing. See more [about writing and distributing plugins](/developer-guide/intro-plugins).
+An alternative way to install a plugin is to place a Python file in the `/home/pioreactor/.pioreactor/plugins` directory on the Raspberry Pi. This is good for one-off scripts or plugins you are demoing or testing. See more [about writing and distributing plugins](/developer-guide/intro-plugins).

user-guide/30-Advanced/02-growth-rate-model.md

@@ -95,7 +95,7 @@ To upload your optical density and dosing events data to the Pioreactor, you nee
 
 :::tip
 
-If using the Pioreactor UI to export datasets _Optical density_ and _Dosing event log_, these already have the correct schema. Use the "Partition output files by Pioreactor" to split the exports into individual CSV files per Pioreactor unit.
+If using the Pioreactor UI to export datasets _Optical density_ and _Dosing event log_, these already have the correct schema.
 
 
 :::
@@ -106,10 +106,11 @@ If using the Pioreactor UI to export datasets _Optical density_ and _Dosing even
 | -------------------------------- | ------------- | ------------------ | ------------------------------------------------------------------------------------------------------------- |
 | `od_reading`                     | Yes             | **float**        | Raw or pre-normalized optical-density measurement.                                                            |
 | `hours_since_experiment_created` | Yes             | **float**        | Elapsed hours since the experiment’s “time 0”. Use decimals for sub-hour resolution (e.g. `0.4167` ≈ 25 min). |
+| `pioreactor_unit` | No             | **string**        | use this column to partition different experiments or units |
 
 :::info
 
-Additional columns (sensor angle, experiment name, etc.) are ignored by the parser, so feel free to keep them. Also, the uploaded CSV should only reference a single unit, so if you have multiple units, you should have multiple CSVs.
+Additional columns (sensor angle, experiment name, etc.) are ignored by the parser, so feel free to keep them.
 
 
 
@@ -124,6 +125,16 @@ od_reading,hours_since_experiment_created
 0.1749,0.402
 ```
 
+#### Multiple units example
+
+```csv
+pioreactor_unit,od_reading,hours_since_experiment_created
+A,0.1725,0.397
+A,0.1735,0.399
+B,0.1249,0.397
+B,0.1280,0.399
+```
+
 ---
 
 ### 2. Dosing-events CSV
@@ -133,6 +144,8 @@ od_reading,hours_since_experiment_created
 | `event`                          | Yes             | **category** (string) | Either `add_media`, `add_alt_media`, or `remove_waste`.      |
 | `volume_change_ml`               | Yes             | **float**           | volume change (mL) |
 | `hours_since_experiment_created` | Yes             | **float**           | Timestamp in **hours**, exactly matching the OD clock.                                        |
+| `pioreactor_unit` | No             | **string**        | use this column to partition different experiments or units |
+
 
 #### Minimal example