From 68a53bfe9f2be688cc6b881af7564dbb032444dc Mon Sep 17 00:00:00 2001 From: Matt Williamson <87771120+mattw-nws@users.noreply.github.com> Date: Mon, 28 Aug 2023 14:05:49 -0500 Subject: [PATCH] Apply typographical suggestions from code review Co-authored-by: Phil Miller - NOAA --- include/core/HY_Features.hpp | 2 +- include/core/Layer.hpp | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/include/core/HY_Features.hpp b/include/core/HY_Features.hpp index 520a9cd872..6e74939204 100644 --- a/include/core/HY_Features.hpp +++ b/include/core/HY_Features.hpp @@ -60,7 +60,7 @@ namespace hy_features { /** * @brief Construct a new HY_Features object from a Network and a set of formulations. * - * Constructs the HY_Catchment objects for each catchment connecting them with the provided link_key attaches tha formaulation + * Constructs the HY_Catchment objects for each catchment connecting them with the provided link_key attaches the formulation * associated with the catchment found in the Formulation_Manager. Also constucts each nexus as a HY_PointHydroNexus. * * @param catchments diff --git a/include/core/Layer.hpp b/include/core/Layer.hpp index 08d992bfd6..e25fa66884 100644 --- a/include/core/Layer.hpp +++ b/include/core/Layer.hpp @@ -43,13 +43,13 @@ namespace ngen virtual ~Layer() {} /*** - * @brief Return the next timestep that will be processed by this layer in epoc time units + * @brief Return the next timestep that will be processed by this layer in epoch time units */ time_t next_timestep_epoch_time() { return simulation_time.next_timestep_epoch_time(); } /*** - * @brief Return the last timesteo that was processed by this layer in epoc time units + * @brief Return the last timestep that was processed by this layer in epoch time units */ time_t current_timestep_epoch_time() { return simulation_time.get_current_epoch_time(); } @@ -113,7 +113,7 @@ namespace ngen double response_m_h = response_m_s / 3600.0; //update the nexus with this flow for(auto& nexus : features.destination_nexuses(id)) { - //TODO in a DENDRIDIC network, only one destination nexus per catchment + //TODO in a DENDRITIC network, only one destination nexus per catchment //If there is more than one, some form of catchment partitioning will be required. //for now, only contribute to the first one in the list nexus->add_upstream_flow(response_m_h, id, output_time_index);