News: 25 years on printing: Fixed typo

Author: tillkamppeter

_posts/2025-08-01-OpenPrinting News - 25 years of working full-time for printing with free open-source-software.md

@@ -36,7 +36,7 @@ One was CUPS' simple but fully automatic **broadcasting/browsing system**, where
 
 This mechanism got replaced by the **DNS-SD** protocol, which is once a general standard in networking, and also matches the standard of driverless [IPP](https://en.wikipedia.org/wiki/Internet_Printing_Protocol) printing. Only here the automatic creation of virtual print queues on the client side was not done, which made me create [cups-browsed](/achievements/#cups-browsed), an auxiliary daemon which creates local print queues for discovered IPP printers, both shared remote CUPS queues and network printers.
 
-When **Apple removed the filters and backends from CUPS** (they had hired Michael full-time for macOS printing from 2007 tom 2019) **as they have their own proprietary ones** (2011) I had overtaken their maintainership calling it the [cups-filters](/achievements/#cups-filters) project and the first thing I did was switching them over to the [PDF-centric printing workflow](/achievements/#pdf-instead-of-postscript-as-standard-print-job-format) which we already had agreed on on the OpenPrinting Summit back in 2006, making all distros finally getting switched to PDF.
+When **Apple removed the filters and backends from CUPS** (they had hired Michael full-time for macOS printing from 2007 to 2019) **as they have their own proprietary ones** (2011) I had overtaken their maintainership calling it the [cups-filters](/achievements/#cups-filters) project and the first thing I did was switching them over to the [PDF-centric printing workflow](/achievements/#pdf-instead-of-postscript-as-standard-print-job-format) which we already had agreed on on the OpenPrinting Summit back in 2006, making all distros finally getting switched to PDF.
 
 I also created the idea of the [Common Print Dialog Backends](/achievements/#common-print-dialog-backends) to separate the communication with the actual print technology (like CUPS) from the print dialog GUI. This is once to overcome the inertia of big GUI toolkit and app projects of keeping pace with changes in the print system (CUPS), as motivation of printing support maintenance work in these GUI/desktop project is very low. So the maintainer of the print dialog maintains the backend to keep up with the changes in CUPS. Also backends for cloud printing services could easily get added (and so the support for them be added to all print dialogs by installing a single Snap).