fixes

Author: CamDavidsonPilon

developer-guide/07-Plugins/02-adding-plugins-to-ui.md

@@ -21,8 +21,8 @@ You should have already added your plugin's Python code to your Pioreactor by so
 
 
 The list of activities, among other things, is sourced from either of two directories:
- - `/var/www/pioreactorui/contrib/jobs/`, is the source of the "default" jobs
- - `/home/pioreactor/.pioreactor/plugins/ui/contrib/jobs`, is a directory to put custom yaml files for jobs.
+ - `~/pioreactor/.pioreactor/ui/jobs`, is the source of the "default" jobs
+ - `~/pioreactor/.pioreactor/plugins/ui/jobs`, is a directory to put custom yaml files for plugins.
 
 Placing a new yaml file in either of these folders will populate the page with your new job. Here's an example `example.yaml` file:
 
@@ -63,8 +63,8 @@ Saving it to either directory above, and refreshing the page:
 
 Placing a new yaml file in either of the following folders will populate the UI with your new job.
 
- - `/var/www/pioreactorui/contrib/jobs/`, is the source of the "default" jobs
- - `/home/pioreactor/.pioreactor/plugins/ui/contrib/jobs/`, is a directory to put custom plugins.
+ - `~/pioreactor/.pioreactor/ui/jobs`, is the source of the "default" jobs
+ - `~/pioreactor/.pioreactor/plugins/ui/jobs`, is a directory to put custom yaml files for plugins.
 
 ```yaml
 ---
@@ -87,8 +87,11 @@ Suppose we wish to add our new automation, either installed from a package or vi
 ![](/img/developer-guide/07-plugins/02-adding-plugins-to-ui/dropdown_automations.png)
 
 This list is sourced from yaml files located on the leader's Raspberry Pi, in either of two directories:
- - `/var/www/pioreactorui/contrib/automations/`, is the source of the our built-in automations
- - `/home/pioreactor/.pioreactor/plugins/ui/contrib/automations/{led,dosing,temperature}`, is a directory to put yaml files for custom automations.
+
+ - `~/pioreactor/.pioreactor/ui/automations`, is the source of the "default" automations
+ - `~/pioreactor/.pioreactor/plugins/ui/automations`, is a directory to put custom yaml files for plugins.
+
+
 
 Placing your yaml file in either folder above will populate the dropdown list in the UI with your new automation. Here's an example `example.yaml` file:
 

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

@@ -149,7 +149,7 @@ function decorated with `@run.command` at the bottom of the file. See example [h
 
 #### 3. Optional: A configuration file, named `additional_config.ini`
 
-This configuration file will contain additional configs that we want to add to our list of existing Configurations on the Pioreactor web interface. This file will be merged with the existing `config.ini` when the plugin is installed. 
+This configuration file will contain additional configs that we want to add to our list of existing Configurations on the Pioreactor web interface. This file will be merged with the existing `unit_config.ini` when the plugin is installed.
 
 ![](/img/developer-guide/07-plugins/03-plugin-as-python-package/python-package-new-config.png)
 

user-guide/01-getting-started/00-gettingstarted.mdx

@@ -26,18 +26,21 @@ import Card from '@site/src/components/Card';
     <Card imageUrl="user-guide/hardware-assembly/pioreactor_20ml_v1.0_splash.png" headerText="Pioreactor 20ml v1.0" linkUrl="/user-guide/hardware-setup-intro"/>
 </div>
 
-<h3> Upgrade kits and accessories</h3>
+<h3> Upgrade kits</h3>
 
 <div className="cardGrid">
-    <Card imageUrl="user-guide/hardware-assembly/upgrade_kits/40ml1.0to-1.5.webp" headerText="Pioreactor 40ml v1.0 → v1.5 upgrade kit" linkUrl="/user-guide/40ml-v10-upgrade-v15-upgrade-disassembly"/>
-    <Card imageUrl="user-guide/hardware-assembly/upgrade_kits/20ml_1.1to-1.5_1.webp" headerText="Pioreactor 20ml v1.1 → v1.5 upgrade kit" linkUrl="/user-guide/20ml-v11-upgrade-v15-upgrade-disassembly" />
     <Card imageUrl="user-guide/hardware-assembly/upgrade_XR/40ml-xr.png" headerText="Pioreactor 40ml v1.5 → XR upgrade kit" linkUrl="/user-guide/40ml-v15-to-XR-upgrade-disassembly" isNew={true} />
     <Card imageUrl="user-guide/hardware-assembly/upgrade_XR/20ml-xr.png" headerText="Pioreactor 20ml v1.5 → XR upgrade kit" linkUrl="/user-guide/20ml-v15-to-XR-upgrade-disassembly" isNew={true} />
+    <Card imageUrl="user-guide/hardware-assembly/upgrade_kits/40ml1.0to-1.5.webp" headerText="Pioreactor 40ml v1.0 → v1.5 upgrade kit" linkUrl="/user-guide/40ml-v10-upgrade-v15-upgrade-disassembly"/>
+    <Card imageUrl="user-guide/hardware-assembly/upgrade_kits/20ml_1.1to-1.5_1.webp" headerText="Pioreactor 20ml v1.1 → v1.5 upgrade kit" linkUrl="/user-guide/20ml-v11-upgrade-v15-upgrade-disassembly" />
     <Card imageUrl="user-guide/hardware-assembly/upgrade-version-splash.png" headerText="Pioreactor 20ml v1.0 → v1.1 upgrade kit" linkUrl="/user-guide/v11-upgrade-hardware-setup"/>
     <Card imageUrl="user-guide/add-teh/14_teh_finished.jpeg" headerText="Temperature Expansion Kit" linkUrl="/user-guide/temperature-expansion-kit" />
+</div>
+
+<h3> Accessories</h3>
+
     <Card imageUrl="user-guide/hardware-assembly/pioreactor_dosing_splash.webp" headerText="Adding peristaltic pumps" linkUrl="/user-guide/using-pumps" />
     <Card imageUrl="user-guide/01-getting-started/00-gettingstarted/leds_splash.webp" headerText="Adding more LEDs" linkUrl="/user-guide/using-leds" />
-</div>
 
 <h3> Software guides</h3>
 

user-guide/29-Automations/02-dosing-automations.md

@@ -8,7 +8,7 @@ sidebar_class_name: sidebar-item--updated
 
 When pairing the Pioreactor with dosing pumps, there are new capabilities and experiments you can run. The Pioreactor is pre-programmed with the following dosing automations. In the below automations, values highlighted `like so` are configurable.
 
-Before starting a dosing automation from the UI, review the `Current volume` and `Max working volume` fields in the automation dialog. `Current volume` should match the liquid currently in the vial, and `Max working volume` should match the volume set by the height of your waste / efflux tube.
+Before starting a dosing automation from the UI, review the `Current volume` and `Efflux tube level` fields in the automation dialog. `Current volume` should match the liquid currently in the vial, and `Efflux tube level` should match the volume set by the height of your waste / efflux tube.
 
 ## Available dosing automations
 
@@ -155,12 +155,12 @@ To further avoid overflow, we limit how much liquid is added in a single pump cy
 
 
  - **Current volume**: this is how much liquid is currently in the vial when you start the automation.
- - **Max working volume**: the efflux tube's position determines the maximum volume your liquid volume will reach.
+ - **Efflux tube level**: the efflux tube's position determines the maximum volume your liquid volume will reach.
 
 
 ###  Configuration parameters
 
-You can edit these parameters in your config.ini files. For dosing runs started from the UI, `Current volume` and `Max working volume` can also be adjusted directly in the automation dialog before starting.
+You can edit these parameters in your config.ini files. For dosing runs started from the UI, `Current volume` and `Efflux tube level` can also be adjusted directly in the automation dialog before starting.
 
 
 #### Section `[dosing_automation.config]`