From: Arnaud Giersch <arnaud.giersch@univ-fcomte.fr>
Date: Mon, 3 Oct 2022 12:25:18 +0000 (+0200)
Subject: Minor polishing.
X-Git-Tag: v3.32~3
X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/e0877e83e3fbfa88e8b5c664e811ba22ab1ac4bb

Minor polishing.

[ci-skip]
---

diff --git a/ChangeLog b/ChangeLog
index 26aea30237..fbe83b846e 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -7,10 +7,10 @@ General:
  - Tested with clang (v11, v13, v14 and v16), gcc (v7 to v13) and IntelCC v2022.2
 
 S4U:
- - API evolutions: 
+ - API evolutions:
    - kill signal Comm::on_completion that was not working anyway.
    - Expose signals Activity::on_suspend and Activity::on_resume
-   - New macro xbt_enforce(): similar to xbt_assert(), but throws an AssertionError 
+   - New macro xbt_enforce(): similar to xbt_assert(), but throws an AssertionError
      instead of calling abort().
    - New: s4u::Exec::get_thread_count()
  - Various cleanups around virtual machines:
@@ -81,12 +81,12 @@ Model-Checker:
 
 Fixed bugs (FG#.. -> FramaGit bugs; FG!.. -> FG merge requests)
  (FG: issues on Framagit; GH: issues on GitHub)
- - FG!98: Re-enable the tests for legacy stochastic profiles
  - FG#105: "Variable penalty should not be negative!" with in-flight messages and bandwidth profiles
  - FG#109: Application time reported by --cfg=smpi/display-timing:yes is wrong
- - FG!109: Trigger new engine solve upon host events such as host on/off
  - FG#110: Wait_any does not trigger new model solve when host events occur
  - FG#111: Wrong execution time in rare cases when using multicore
+ - FG!98: Re-enable the tests for legacy stochastic profiles
+ - FG!109: Trigger new engine solve upon host events such as host on/off
  - FG!116: SMPI/replay: Fix issue with recv of size =0
 
 ----------------------------------------------------------------------------
diff --git a/NEWS b/NEWS
index 3664c09506..1a0ae4b2a0 100644
--- a/NEWS
+++ b/NEWS
@@ -9,6 +9,7 @@ __   _____ _ __ ___(_) ___  _ __   |___ / |___ /___ \
   * Improved Python platform generation (more robust, easier to use)
   * Further complete Python bindings (Comm, Engine, ptasks)
   * (+ internal refactoring, MANY bug fixes and documentation improvement)
+
                     _               _____  _____ _
 __   _____ _ __ ___(_) ___  _ __   |___ / |___ // |
 \ \ / / _ \ '__/ __| |/ _ \| '_ \    |_ \   |_ \| |
@@ -22,6 +23,7 @@ The ненасильство release. We stand against war.
   * Introducing BMF sharing, enabling ptasks in regular models (experimental)
   * Further complete Python bindings (Mutex, Semaphore and Barrier)
   * (+ internal refactoring, many bug fixes and documentation improvement)
+
                     _               _____  _____  ___
 __   _____ _ __ ___(_) ___  _ __   |___ / |___ / / _ \
 \ \ / / _ \ '__/ __| |/ _ \| '_ \    |_ \   |_ \| | | |
diff --git a/docs/source/Release_Notes.rst b/docs/source/Release_Notes.rst
index 5a9d72c832..39988fd9b6 100644
--- a/docs/source/Release_Notes.rst
+++ b/docs/source/Release_Notes.rst
@@ -533,7 +533,7 @@ Version 3.32 (not released yet)
 
 This release introduces tons of bugs fixes overall, and many small usability improvements contributed by the community.
 
-**On the bindings front**, we further completed the Python bindings: the whole C++ API of Comms is now accessible (and examplified) in Python, while a
+**On the bindings front**, we further completed the Python bindings: the whole C++ API of Comms is now accessible (and exemplified) in Python, while a
 few missing functions have been added to Engine and Mailboxes. It is also possible to manipulate ptasks from Python.
 
 The Python platform generation has also been improved. In particular, user's errors should now raise an exception instead of killing the interpreter.