Fix wording

README_v2024.md

@@ -18,7 +18,7 @@ colorlinks: true
 
 
 A first evaluation of PipeWire 0.3.59 on R-Car was done with Apertis v2023.
-Because the results present some artefacts, the same evaluation is repeated
+Because the results present some artefacts, the same evaluation has been repeated
 with Apertis v2024pre and [PipeWire 0.3.84](https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.84).
 
 Please refer to the [first report](https://gitlab.apertis.org/daissi/pipewire-evaluation/-/blob/main/README.md)
@@ -131,10 +131,7 @@ stream redirected to 1 output) to evaluate how the sound is affected.
 
 Like for the previous evaluation , it's not possible to reconfigure a running
 device. That means, to reconfigure the sample rate input, we have to force the
-device input to be idle. **NOTE:** there was a bug in pipewire 0.3.79 where nodes
-don't switch to idle status when they are no longer in use preventing the
-reconfiguration of the capture rate. Consequently, a new version (0.3.84) of
-pipewire was imported in Apertis v2024.
+device input to be idle.
 
 During the test, two wav files are generated `test-case-capture1.wav` and
 `test-case-capture2.wav` (both are available in `results_v2024/test-case-2/`).