Update docs/blog/20240624-Daeraxa-3kStars.md

Co-authored-by: Andrew Dupont <[email protected]>

Author: Daeraxa

docs/blog/20240624-Daeraxa-3kStars.md

@@ -96,7 +96,8 @@ We had some big tasks ahead of us; changes needed to be made, and work needed to
 
 - **Building from source:** Atom had a rather complicated (and now rather fragile) way of [bootstrapping](https://atom-flight-manual-archive.github.io/hacking-atom/sections/hacking-on-atom-core/#cloning-and-bootstrapping) itself for development. One of the first tasks was to simplify this to a process that we think is much more robust and much more familiar to those using Node and Electron. This makes it much easier to get involved with Pulsar development.
 
-- **Rebranding** - We had to start removing Atom references and replacing them with Pulsar ones. This was not an easy "find and replace" job as `atom` is used extensively within the APIs and code and therefore something we had to be careful of. We also had to decide on a new logo for the project and add it to the application, along with updates to redirect links within Pulsar to our new repositories, websites, forums, etc.
+- **Rebranding:** We had to start removing Atom references and replacing them with references to Pulsar. We also had to decide when _not_ to remove Atom references; for instance, `atom` is used extensively within the APIs and changing that would’ve broken a lot of code with little justification. We also had to decide on a new logo for the project and add it to the application along with updates to GitHub and social media site links.
+
 - **Decaffeination** - Atom was originally written mostly in [CoffeeScript](https://coffeescript.org/), a rather useful language at the time that compiles to JavaScript. With more and more functionality being introduced into JavaScript, CoffeeScript was quickly becoming obsolete and actually started creating a barrier to entry for contribution rather than easing it, as was the initial intention. The original Atom team had started this process, but over time we were able to achieve the goal of complete decaffeination in Pulsar 1.109 and in PPM in 1.110.
 - **CI and build** - We needed an automated platform to build our binaries and run tests. For this, we went with [CirrusCI](https://cirrus-ci.org/) which had a more than generous free tier, and it reliably built our binaries and ran our tests for over a year. We have since had to [move away](https://pulsar-edit.dev/blog/20230903-confused-Techie-pulsars-ci.html) from CirrusCI.
 - **Versioning** - Atom's last (at the time) release was Atom 1.60, which left us with some issues. We wanted to stay with [Semantic Versioning](https://semver.org/) as Atom had, but what should our first full release be? We could reset the counter back to 1.0, but that would cause packages looking for a minimum version of Atom to break. We could move to 2.0, but again, there was an issue with packages, which were specifically looking only for 1.x versions, but this time as a *maximum* version. We could continue the numbering from Atom, but this seemed like we weren't getting a clean break as a new project. In the end, we decided to jump from 1.60 to 1.100 - a number that would give us a clean start whilst avoiding the issues with package version limits.