Fix typos in release notes.

docs/release-notes/v2.4.0.md

@@ -15,7 +15,7 @@ This is mitigated in two ways:
 - Key methods that were deprecated in favor of new API ones are kept for
   two more minor versions, and are still tested to work as before.
 
-Any end-user encountering issues due to the released or planned evolutions of
+Any end-user encountering issues due to the released or planned evolution of
 DecLearn is invited to contact us via GitLab, GitHub or e-mail so that we can
 provide with assistance and/or update our roadmap so that changes do not hinder
 the usability of DecLearn 2.x for research and applications.
@@ -28,7 +28,7 @@ paving the way towards the next major release, while trying as much as possible
 not to break end-user code.
 
 To avoid unforeseen incompatibilities and cryptic bugs from arsing, from this
-version onwards, the server and clients are expected and verified to use the
+version onward, the server and clients are expected and verified to use the
 same `major.minor` version of DecLearn.
 This policy may be updated in the future, e.g. to specify that clients may
 have a newer minor version than the server (and most probably not the other
@@ -43,7 +43,7 @@ they might have.
 
 ## Revise all aggregation APIs
 
-### Revise the overal design for aggregation and introduce `Aggregate` API
+### Revise the overall design for aggregation and introduce `Aggregate` API
 
 This release introduces the `Aggregate` API, which is based on an abstract base
 dataclass acting as a template for data structures that require sharing across
@@ -237,7 +237,7 @@ disk).
 ### Add a verbosity option for `FederatedClient` and `TrainingManager`.
 
 `FederatedClient` and `TrainingManager` now both accept a `verbose: bool=True`
-instantiatation keyword argument, that changes:
+instantiation keyword argument, that changes:
 
 - (a) the default logger verbosity level: if `logger=None` is also passed,
   the default logger will have 'info'-level verbosity if `verbose` and
@@ -274,7 +274,8 @@ Older TensorFlow versions (v2.5 to 2.10 included) were improperly marked as
 supported in spite of `TensorflowOptiModule` requiring at least version 2.11
 to work (due to changes of the Keras Optimizer API). This has been corrected.
 
-The latest TensorFlow version (v2.16) introduces backward-breaking changes, due to the backend swap from Keras 2 to Keras 3. Our backend code was updated to
+The latest TensorFlow version (v2.16) introduces backward-breaking changes, due
+to the backend swap from Keras 2 to Keras 3. Our backend code was updated to
 both add support for this newer Keras backend, and preserve existing support.
 
 Note that at the moment, the CI does not support TensorFlow above 2.13, due to