Apply suggestions from code review

Author: mhsmith

content/news/buzz/august-2025-status-update/contents.lr

@@ -4,21 +4,21 @@ author: Russell Keith-Magee
 ---
 body:
 
-August has been a slow month due to some personal leave, and some unexpected road bumps from Github - but BeeWare has still made some notable progress.
+August has been a slow month due to some personal leave, and some unexpected road bumps from GitHub - but BeeWare has still made some notable progress.
 
 ## What we've done
 
 - [Python 3.14.0rc2 has been released](https://www.python.org/downloads/release/python-3140rc2/) - including, for the first time, official Android binaries! You can now download official, pre-compiled Android binaries for CPython. This is a major milestone for Android support, as it means BeeWare is able to use official binaries when building Android apps. 
-- As part of the changes adding official Android binaries to the release process, [Android was added to the CI checks that are performed as part of every pull request on Github](https://github.com/python/cpython/pull/137186). This will significantly reduce the likelihood of bugs landing in main that will break the Android buildbots.
+- As part of the changes adding official Android binaries to the release process, [Android was added to the CI checks that are performed as part of every CPython pull request on GitHub](https://github.com/python/cpython/pull/137186). This will significantly reduce the likelihood of bugs landing in main that will break the Android buildbots.
 - We spent a significant amount of time [dealing with an update to  GitHub Actions](https://github.com/actions/runner-images/issues/12777). On August 11, GitHub rolled out an update to the disk image they use for macOS 15 machines - and in the process, broke the tools that BeeWare uses to test iOS applications. It took almost a week to identify the cause of this problem, and develop a fix. However, the good news is that [the fix significantly simplifies the iOS testing process](https://github.com/python/cpython/pull/138018).
-- We [began the process of adding official builds for iOS](https://github.com/python/cpython/pull/138176). The complexity of iOS multi-architecture builds makes official builds a little more complicated than Android, but we're hopeful this work will be able to land in the near future.
+- We [began the process of adding official Python binaries for iOS](https://github.com/python/cpython/pull/138176). The complexity of iOS multi-architecture builds makes official builds a little more complicated than Android, but we're hopeful this work will be able to land in the near future.
 - We added a recipe for building [iOS binaries for zstandard](https://github.com/beeware/cpython-apple-source-deps/pull/64). These are needed to support the new zstandard compression library in Python 3.14.
-- We released a [website to track the status of binary wheel support for iOS and Android](https://beeware.org/mobile-wheels/)
+- We released a [website to track the status of binary wheel support for iOS and Android](https://beeware.org/mobile-wheels/).
 - We released [Briefcase 0.3.25](http://pypi.org/project/briefcase/0.3.25/). This release was primarily required because of a change to Android Play Store target SDK requirements.
 - We modified how Briefcase [determines the minimum supported macOS/iOS version that Python requires](https://github.com/beeware/briefcase/pull/2443). This change allows us to simplify the contents of the support packages.
-- We made Briefcase [more resilient to badly packaged binary wheels](https://github.com/beeware/briefcase/pull/2429). Many packages publish `py3-none-any` wheels, which *should* be platform independent - but then include platform-specific binaries or dynamic library content in the wheels. Briefcase will now ignore these files.
+- We made Briefcase [more resilient to badly packaged binary wheels on macOS](https://github.com/beeware/briefcase/pull/2429). Many packages publish `py3-none-any` wheels, which *should* be platform independent - but then include platform-specific binaries or dynamic library content in the wheels. Briefcase will now ignore these files.
 - Briefcase's unit tests have been made [more resilient to temporary network outages](https://github.com/beeware/briefcase/pull/2434) - something that happens surprisingly often in the GitHub Actions environment.
-- We dropped support for Python 3.9, and added support for Python 3.14 across BeeWare projects. For the first time, this includes the ability to release Windows support [based on pre-releases of Python](https://github.com/beeware/briefcase/pull/2432) - previously, we had to wait until the `.0` release of a new python version before we could add support.
+- We dropped support for Python 3.9, and added support for Python 3.14 across BeeWare projects. For the first time, this includes the ability to release Windows support [based on pre-releases of Python](https://github.com/beeware/briefcase/pull/2432) - previously, we had to wait until the `.0` release of a new Python version before we could add support.
 - We [improved the checks (and error reporting) associated with using new versions of Travertino with old versions of Toga](https://github.com/beeware/toga/pull/3683).
 - We resolved a long standing bug on iOS where [touch events wouldn't be triggered if content was "below the fold" on a scroll container](https://github.com/beeware/toga/pull/3680).
 - We started work on a [new tool to consolidate the cross-platform building tools used on Android, iOS and Emscripten](https://github.com/beeware/xbuild). This tool still needs a lot of work before it's production-ready, but it draws from our lessons learned on cibuildwheel, and should allow us to simplify and consolidate the approaches taken to implement cross-platform builds.