style: fix docs

Signed-off-by: F.N. Claessen <felix@seita.nl>
FlexMeasures · Oct 31, 2023 · 93a374f · 93a374f
1 parent dc4bdc2
commit 93a374f
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/documentation/api/change_log.rst b/documentation/api/change_log.rst
@@ -8,7 +8,7 @@ API change log
 v3.0-13 | 2023-10-31
 """"""""""""""""""""
 
-- Introduced the ``site-consumption-capacity`` and ``site-production-capacity`` to the ``flex-context``field for `/sensors/<id>/schedules/trigger` (POST).
+- Introduced the ``site-consumption-capacity`` and ``site-production-capacity`` to the ``flex-context`` field for `/sensors/<id>/schedules/trigger` (POST).
 
 v3.0-12 | 2023-09-20
 """"""""""""""""""""

diff --git a/documentation/api/notation.rst b/documentation/api/notation.rst
@@ -238,8 +238,8 @@ With the flexibility context, we aim to describe the system in which the flexibl
 - ``consumption-price-sensor`` ― the sensor which defines costs/revenues of consuming energy
 - ``production-price-sensor`` ― the sensor which defines cost/revenues of producing energy
 - ``site-power-capacity`` ― defaults to the Asset attribute ``capacity_in_mw`` ― maximum/minimum achievable power at the grid connection point.
-- ``site-consumption-capacity`` ― defaults to the Asset attribute ``consumption_capacity_in_mw`` ― maximum consumption power at the grid connection point.
-- ``site-production-capacity`` ― defaults to ``site-power-capacity`` or the Asset attribute ``production_capacity_in_mw`` ― maximum production power at the grid connection point.
+- ``site-consumption-capacity`` ― defaults to ``site-power-capacity`` or otherwise to the Asset attribute ``consumption_capacity_in_mw`` ― maximum consumption power at the grid connection point.
+- ``site-production-capacity`` ― defaults to ``site-power-capacity`` or otherwise to the Asset attribute ``production_capacity_in_mw`` ― maximum production power at the grid connection point.
 
 These should be independent on the asset type and consequently also do not depend on which scheduling algorithm is being used.
 

diff --git a/documentation/changelog.rst b/documentation/changelog.rst
@@ -12,7 +12,7 @@ v0.17.0 | November XX, 2023
 New features
 -------------
 
-- Different site-level production and consumption limits can be defined for the storage scheduler via the API (``flex-context``) or the asset attributes [see `PR #884 <https://github.com/FlexMeasures/flexmeasures/pull/884>`_]
+- Different site-level production and consumption limits can be defined for the storage scheduler via the API (``flex-context``) or via asset attributes [see `PR #884 <https://github.com/FlexMeasures/flexmeasures/pull/884>`_]
 - Scheduling data better distinguishes (e.g. in chart tooltips) when a schedule was the result of a fallback mechanism, by splitting off the fallback mechanism from the main scheduler (as a separate job) [see `PR #846 <https://github.com/FlexMeasures/flexmeasures/pull/846>`_]
 
 Infrastructure / Support