[DOC] README: British spelling (optimization -> optimisation, optimizer -> optimiser)

README.md

@@ -9,9 +9,9 @@ app_file: app.py
 pinned: false
 ---
 
-# Carbon Dioxide Removal Optimizer
+# Carbon Dioxide Removal Optimiser
 
-A Streamlit app for optimizing carbon removal portfolios across different methods and constraints.
+A Streamlit app for optimising carbon removal portfolios across different methods and constraints.
 
 ---
 
@@ -83,8 +83,8 @@ The app has seven tabs, accessible from the left sidebar:
 | Welcome | Welcome | Introduction, instructions, and a quick-start guide |
 | Resource inputs | Resource inputs | Set the available quantity of each resource; add custom resource batches |
 | Method constraints | Method constraints | Activate or deactivate CDR methods; set caps and constraints per method |
-| Resource coefficients | Resource coefficients | View and adjust the coefficient values (min / median / max) used by the optimizer |
-| Portfolio generation | Portfolio generation | Run the LP optimizer and view results (charts, tables, resource usage) |
+| Resource coefficients | Resource coefficients | View and adjust the coefficient values (min / median / max) used by the optimiser |
+| Portfolio generation | Portfolio generation | Run the LP optimiser and view results (charts, tables, resource usage) |
 | Sensitivity analysis | Sensitivity analysis | Analyse how binding each resource constraint is; identify bottlenecks |
 | Scenario comparison | Scenario comparison | Save the current scenario, load a previous one, and compare multiple runs side by side |
 
@@ -94,7 +94,7 @@ The app has seven tabs, accessible from the left sidebar:
 
 In the **Resource inputs** tab, users can add custom resource batches — named resources that substitute for a standard or "Other" reference resource within a specific CDR method.
 
-For example, a user might add a batch called "Basalt A" linked to the reference group "Basalt mineral" and assign it to the Enhanced weathering method. The optimizer will then use the batch's custom coefficients instead of the standard reference values for that method.
+For example, a user might add a batch called "Basalt A" linked to the reference group "Basalt mineral" and assign it to the Enhanced weathering method. The optimiser will then use the batch's custom coefficients instead of the standard reference values for that method.
 
 Custom batches are stored in the session and saved when exporting a scenario. They do **not** require any change to `inputs_aggregated.csv`.
 
@@ -104,7 +104,7 @@ Custom batches are stored in the session and saved when exporting a scenario. Th
 
 In the **Scenario comparison** tab, users can:
 
-- **Export** the current state (resource caps, method constraints, coefficients, optimization results) as a `.zip` file or an Excel `.xlsx` file
+- **Export** the current state (resource caps, method constraints, coefficients, optimisation results) as a `.zip` file or an Excel `.xlsx` file
 - **Import** a previously exported scenario file to restore a complete session state
 - **Compare** multiple saved scenarios side by side in the charts
 
@@ -282,7 +282,7 @@ Each row represents **one resource used by one CDR method**, with the following
 
 > **Naming convention — "Other" resources:** any resource whose name starts with `Other ` (capital O, followed by a space — e.g. `Other land`, `Other water`) is **hidden from the standard resource display** in Tabs 1 and 3. It still functions normally in the model and remains available as a reference group in the "Add resource" dialog. Use this convention intentionally when you want a resource to be inherited by custom user-defined batches but not shown as a standalone input row.
 
-> **Naming convention — "Other" methods:** any CDR method whose name starts with `Other` receives special treatment in the optimizer. Instead of appearing as a fixed method, the LP automatically creates **one variant per custom resource batch** the user adds that is linked to that method. This is intended for generic CDR pathways where the type of resource is user-defined. If you add a method using this naming convention, make sure it is intentional.
+> **Naming convention — "Other" methods:** any CDR method whose name starts with `Other` receives special treatment in the optimiser. Instead of appearing as a fixed method, the LP automatically creates **one variant per custom resource batch** the user adds that is linked to that method. This is intended for generic CDR pathways where the type of resource is user-defined. If you add a method using this naming convention, make sure it is intentional.
 
 ---
 
@@ -363,7 +363,7 @@ You should see `(venv)` at the start of your terminal line.
 
 **When to use:** A new carbon removal approach needs to be added to the tool.
 
-> ⚠️ **"Other" method naming:** if the method name starts with `Other` (e.g. `Other CDR`), the optimizer treats it specially — it creates one variant per custom resource batch that the user links to this method, instead of running it as a fixed method. Only use this naming if that expansion behavior is intentional. For a standard CDR method with defined resource inputs, use a name that does not start with `Other`.
+> ⚠️ **"Other" method naming:** if the method name starts with `Other` (e.g. `Other CDR`), the optimiser treats it specially — it creates one variant per custom resource batch that the user links to this method, instead of running it as a fixed method. Only use this naming if that expansion behavior is intentional. For a standard CDR method with defined resource inputs, use a name that does not start with `Other`.
 
 **Option 1 - On Hugging Face**
 
@@ -615,7 +615,7 @@ This section explains how to keep the tool's software dependencies up to date, s
 
 ### What is a library (dependency)?
 
-The tool is built on top of external software packages ("libraries") that handle things like displaying the interface, reading Excel files, or running the optimization. These libraries are listed in `requirements.txt` with their exact version numbers (e.g., `streamlit==1.45.1`).
+The tool is built on top of external software packages ("libraries") that handle things like displaying the interface, reading Excel files, or running the optimisation. These libraries are listed in `requirements.txt` with their exact version numbers (e.g., `streamlit==1.45.1`).
 
 Libraries sometimes release updates - fixing bugs, patching security holes, or adding new features. The risk is that an update can also change how a library behaves and break the tool.
 
@@ -631,7 +631,7 @@ These are the libraries that matter most for this tool:
 | **streamlit-option-menu** | The navigation sidebar menu | 🟡 Medium - must stay compatible with streamlit version |
 | **pandas** | Reads and processes CSV and Excel files | 🟡 Medium - occasional API changes |
 | **numpy** | Numerical operations (arrays, math) | 🟡 Medium - used by scipy and pandas |
-| **scipy** | Runs the LP optimization (`linprog`) | 🟡 Medium - optimization results could change |
+| **scipy** | Runs the LP optimisation (`linprog`) | 🟡 Medium - optimisation results could change |
 | **plotly** | All charts and interactive graphs | 🟡 Medium - chart API evolves |
 | **openpyxl** | Reads and writes Excel files (.xlsx) | 🟢 Low - stable API |
 | **pillow** | Image handling (indirect use) | 🟢 Low |
@@ -675,7 +675,7 @@ openpyxl ──────────────► pillow
 
 #### ✅ Update when needed
 - **Streamlit** - when a new feature in the app requires it, or when a critical bug in the current version is causing problems.
-- **pandas / numpy / scipy** - when a bug in the current version is causing incorrect data processing or optimization results.
+- **pandas / numpy / scipy** - when a bug in the current version is causing incorrect data processing or optimisation results.
 - **openpyxl** - when Excel import/export breaks with newer `.xlsx` files.
 
 #### ❌ Do NOT update just because a newer version exists
@@ -744,7 +744,7 @@ pip freeze > requirements.txt
 - Start the app: `streamlit run app.py`
 - Go through every tab
 - Import and export an Excel file
-- Run an optimization
+- Run an optimisation
 - Check that charts display correctly
 
 **Step 7 - If something breaks**