Skip to content

Commit da4bee0

Browse files
Minor Reword
1 parent d25dbe6 commit da4bee0

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

_posts/2025-01-26-the-future-of-rebble.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ and will accelerate our efforts to produce new hardware.
1717

1818
Previously, we have been working on our own replacement firmware: [RebbleOS](https://github.com/pebble-dev/RebbleOS). As you can see by the commit history though, progress was slow.
1919
Building a production-ready realtime OS for the Pebble is no small feat, and although we were confident we'd get there given enough time, it was never our ideal path.
20-
Thanks to the hard work of many people both within Google and not, we finally have our hands on the original source code for PebbleOS. You can read [their blog post on it here.](https://opensource.googleblog.com/2025/01/see-code-that-powered-pebble-smartwatches.html)
20+
Thanks to the hard work of many people both within Google and not, we finally have our hands on the original source code for PebbleOS. You can read [Google's blog post on this for even more information.](https://opensource.googleblog.com/2025/01/see-code-that-powered-pebble-smartwatches.html)
2121

2222
This does _not_ mean we instantly have the ability to start developing updates for PebbleOS though, we first will need to spend some concentrated time getting it to build.
2323
But before we talk about that, let's talk about Rebble itself.

0 commit comments

Comments
 (0)