fix ` in docs

Author: antonio-leblanc

docs/source/reference/commands.rst

@@ -135,7 +135,7 @@ Creates the smallest possible triangular fire front (an ignition point) at the s
 **Arguments:**
 
 *   ``loc=(x,y,z)``: Starting location using Cartesian coordinates (x,y,z) in meters.
-*   ``lonlat=(lon,lat)``: Starting location using WGS84 coordinates (longitude, latitude). *Use either ``loc`` or ``lonlat``.*
+*   ``lonlat=(lon,lat)``: Starting location using WGS84 coordinates (longitude, latitude). *Use either loc or lonlat.*
 *   ``t=seconds|date=YYYY-MM-DDTHH:MM:SSZ``: Time when the fire is started, either in seconds since simulation start or as an absolute ISO 8601 GMT date/time.
 
 **Example:**
@@ -344,7 +344,7 @@ Triggers a change in simulation data at a specific time and location. Can be use
 
 Prints a representation of the current simulation state (primarily the fire front location) to the console or to a specified file. The output format is determined by the `dumpMode` parameter (set via `setParameter`).
 
-**Output Formats (`dumpMode`):**
+**Output Formats (dumpMode):**
 
 *   `ff`: Native format, potentially re-parsable by ForeFire.
 *   `json`: Compact Cartesian JSON format.

docs/source/user_guide/basic_configuration.rst

@@ -3,13 +3,13 @@ Basic Configuration
 
 ForeFire simulations typically require three main input files to run:
 
-1.  **Fuels File (`.csv`)**: Defines the classes of fuels and their associated parameters used by the fire spread model (e.g., Rothermel).
-2.  **Landscape File (`.nc`)**: A NetCDF file containing geospatial data layers for the simulation domain, typically including:
+1.  **Fuels File (.csv)**: Defines the classes of fuels and their associated parameters used by the fire spread model (e.g., Rothermel).
+2.  **Landscape File (.nc)**: A NetCDF file containing geospatial data layers for the simulation domain, typically including:
 
     - Elevation (Digital Elevation Model - DEM)
     - Fuel types map (matching the indices in the Fuels File)
     - (Optionally) Pre-defined wind fields or other environmental data.
-3.  **ForeFire Script File (`.ff`)**: A text file containing commands and parameters that control the simulation execution. This includes:
+3.  **ForeFire Script File (.ff)**: A text file containing commands and parameters that control the simulation execution. This includes:
 
     - Setting simulation parameters (e.g., propagation model, output format).
     - Loading the landscape and fuels data.

docs/source/user_guide/core_concepts.rst

@@ -20,14 +20,14 @@ Key Simulation Components
 
 The simulation engine relies on several key C++ components (classes) to manage the fire spread process:
 
-*   **`Simulator` & `TimeTable` (Event-Driven Core)**
+*   **Simulator & TimeTable (Event-Driven Core)**
 
     *   ForeFire uses an **event-driven** approach. Instead of fixed time steps for the entire simulation, it maintains a `TimeTable` (a prioritized queue) of future events.
     *   Each event typically corresponds to a `FireNode` needing an update at a specific future time.
     *   The `Simulator` processes events from the `TimeTable` in chronological order. It retrieves the next event, tells the associated object (like a `FireNode`) to update its state and calculate its next move, and then the object schedules its *next* update event back into the `TimeTable`.
     *   **This event-driven approach means the simulation doesn't use fixed global time steps; different parts of the front can advance according to their own calculated timings.**
 
-*   **`FireDomain` (The Simulation World)**
+*   **FireDomain (The Simulation World)**
 
     *   Represents the overall simulation area and context.
     *   Manages the simulation's current time.
@@ -37,7 +37,7 @@ The simulation engine relies on several key C++ components (classes) to manage t
     *   Manages the `TimeTable` of simulation events.
     *   May handle discretization of the domain into cells (e.g., for flux calculations or burning map outputs).
 
-*   **`FireFront` & `FireNode` (Representing the Fire)**
+*   **FireFront & FireNode (Representing the Fire)**
 
     *   ForeFire uses a **Lagrangian** approach to track the fire's edge.
     *   A `FireFront` represents a continuous segment of the fire perimeter. It is essentially a linked list of `FireNode` objects.
@@ -55,7 +55,7 @@ The simulation engine relies on several key C++ components (classes) to manage t
         *   **Splitting:** Not explicitly mentioned in summary, but might occur if front self-intersects or hits complex boundaries.
         *   **Inner Fronts:** `FireFront` s can be nested to represent unburned islands within the main fire perimeter.
 
-*   **`DataBroker` & `DataLayer` (Accessing Environmental Data)**
+*   **DataBroker & DataLayer (Accessing Environmental Data)**
 
     *   The `DataBroker` is the central hub for all environmental data needed by the simulation (terrain, fuel, weather).
     *   It manages a collection of `DataLayer` objects. Each `DataLayer` provides access to a specific type of data (e.g., elevation, fuel index, wind speed).
@@ -69,13 +69,13 @@ The simulation engine relies on several key C++ components (classes) to manage t
         *   Interpolating data in space and potentially time (e.g., for time-varying wind fields).
     *   When a `FireNode` needs environmental data to calculate its speed, it asks the `DataBroker`, which efficiently retrieves the necessary values from the relevant `DataLayer` (s) at the node's location.
 
-*   **`PropagationModel` & `FluxModel` (The Physics)**
+*   **PropagationModel & FluxModel (The Physics)**
 
     *   ForeFire uses a **Strategy pattern** for physical calculations, allowing different models to be plugged in.
     *   `PropagationModel` subclasses (e.g., `Rothermel`, `Balbi`, `Iso`) implement specific algorithms to calculate the Rate of Spread (ROS) based on properties fetched via the `DataBroker`. The active model is chosen using the :ref:`propagationModel <param-propagationmodel>` parameter.
     *   `FluxModel` subclasses (e.g., `HeatFluxBasicModel`) calculate fluxes (like heat, water vapor) from the burning area, often needed for coupled simulations or specific research outputs.
 
-*   **`SimulationParameters` (Configuration)**
+*   **SimulationParameters (Configuration)**
 
     *   A central place (likely a Singleton class internally) holding the global configuration values set by the user via :ref:`setParameter <cmd-setparameter>` or :ref:`setParameters <cmd-setparameters>` commands. This includes things like model choices, resolution parameters, output settings, etc.
 
@@ -88,10 +88,10 @@ Simulation Workflow Summary
     *   Commands from a script file (or interactive input) are processed.
     *   :doc:`Parameters </reference/parameters>` are set.
     *   The :ref:`FireDomain <cmd-firedomain>` is created.
-    *   :ref:`loadData <cmd-loaddata>` populates the `DataBroker` with `DataLayer`s from the :doc:`/user_guide/landscape_file`. The :doc:`/user_guide/fuels_file` information is associated.
+    *   :ref:`loadData <cmd-loaddata>` populates the `DataBroker` with `DataLayer` from the :doc:`/user_guide/landscape_file`. The :doc:`/user_guide/fuels_file` information is associated.
     *   The initial fire state is defined using :ref:`startFire <cmd-startfire>` or custom `FireFront`/`FireNode` commands, scheduling the first update events for the initial nodes into the `TimeTable`.
 
-2.  **Simulation Loop (driven by `step` or `goTo`):**
+2.  **Simulation Loop (driven by step or goTo):**
 
     *   The `Simulator` gets the chronologically next event (usually a `FireNode` update) from the `TimeTable`.
     *   The `Simulator` advances the global simulation time to the event time.