Typos

Pi4J · Mar 19, 2024 · 9b4b886 · 9b4b886
1 parent 73609af
commit 9b4b886
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 3 deletions.
diff --git a/content/about/release-notes.md b/content/about/release-notes.md
@@ -19,9 +19,8 @@ You can find out [more about Alexander in this blog post](/blog/2024/20240318_in
   * This new provider can be used without the need to start a Pi4J application with sudo, so also fixes [#212](https://github.com/Pi4J/pi4j-v2/issues/212) when you only need DigitalInput and/or DigitalOutput.
 * Better handling of mock Plugins: Plugins can now define if they are mocks, and these are not auto-detected anymore. The default target for the Pi4J library is the Raspberry Pi, and thus auto-detecting mocks on the Pi, which are only for tests is counterintuitive.
 * Extended Providers with a priority: this priority helps to determine which Provider should be loaded, when multiple Providers with the same IOType are being loaded by different plugins. This change enforces that a given IOType can only have one Provider loaded at runtime preventing errors when, for instance, two I2C providers are loaded at the same time, concurrently writing to the I2C bus.
-* Fix for: LinuxFile reused scratch buffers ensuring size was usable. But the limit value cannot be modified so later usage failed as an intended overwrite. Pull request [#331](https://github.com/Pi4J/pi4j-v2/pull/331).
+* Fix for: LinuxFile reused scratch buffers ensuring size was usable. But the limit value cannot be modified so later usage failed as an intended overwrite. Pull request [#331](https://github.com/Pi4J/pi4j-v2/pull/331), commit [ed208f2](https://github.com/Pi4J/pi4j-v2/commit/ed208f26cfd2a92978d010495fa1c6b5f8726e12).
 * Fix for: I2C interface should use a restart between the write and read operation. Pull request [#333](https://github.com/Pi4J/pi4j-v2/pull/333).
-* Fix for: LinuxFile reused scratch buffers ensuring size was usable, but the limit value cannot be modified so later usage failed as an intended overwrite. Commit [ed208f2](https://github.com/Pi4J/pi4j-v2/commit/ed208f26cfd2a92978d010495fa1c6b5f8726e12).
 * Fix for: Shutting down pool executor too early. Commit [7909a2d](https://github.com/Pi4J/pi4j-v2/commit/7909a2d64d07d23732e5e31254d4d32d4c4087bd).
 * ProviderProxyHandler got removed, simplifying provider loading, thus no more reflection on the instances.
 * You can now add and remove IO instances at runtime.

diff --git a/content/blog/2024/20240318_interview_alexander_liggesmeyer.md b/content/blog/2024/20240318_interview_alexander_liggesmeyer.md
@@ -8,7 +8,7 @@ tags: ["Interview", "Pi4J"]
 
 ## Interview with Alexander Liggesmeyer about Pi4J for Raspberry Pi 5
 
-Today, [version 2.5.0 of Pi4J got released with many changes, fixes and improvements](/about/release-notes/). The most important one being support for the [Raspberry Pi 5](https://www.raspberrypi.com/products/raspberry-pi-5/). Short after the release of this new board, [several issues were raised on GitHub](https://github.com/Pi4J/pi4j-v2/issues/321) as Pi4J was not compatible. The Raspberry Pi 5 uses a completely new way to interact with the GPIOs: the [RP1 chip](https://www.raspberrypi.com/documentation/microcontrollers/rp1.html). Thanks to this chip, GPIO, SPI, I2C, USB, ethernet,... are seperated from the SoC to make it easier to develop newer boards and support. But this new approach wasn't supported by the PiGpio library used in Pi4J V2... Until Alexander Liggesmeyer took up the challenge to find a solution!
+Today, [version 2.5.0 of Pi4J got released with many changes, fixes and improvements](/about/release-notes/). The most important one being support for the [Raspberry Pi 5](https://www.raspberrypi.com/products/raspberry-pi-5/). Short after the release of this new board, [several issues were raised on GitHub](https://github.com/Pi4J/pi4j-v2/issues/321) as Pi4J was not compatible. The Raspberry Pi 5 uses a completely new way to interact with the GPIOs: the [RP1 chip](https://www.raspberrypi.com/documentation/microcontrollers/rp1.html). Thanks to this chip, GPIO, SPI, I2C, USB, ethernet,... are seperated from the SoC to make it easier to develop newer boards. But this new approach wasn't supported by the PiGpio library used in Pi4J V2... Until Alexander Liggesmeyer took up the challenge to find a solution!
 
 _Thanks Alexander for your amazing work! Can you introduce yourself?_