Small edits

src/assets/resume.toml

@@ -87,7 +87,7 @@ url = "https://www.ualberta.ca/en/information-services-and-technology/index.html
 
 [[education]]
 institution = "University of Saskatchewan"
-degree = "Masters"
+degree = "Master's"
 field = "Computer Science"
 date = "2024 - Present"
 details = [

src/config.ts

@@ -32,7 +32,7 @@ export const config: Config = {
     tagline: "Researcher, Full-Stack Developer, and IT Professional",
     description: "Researcher, Full-Stack Developer, and IT Professional",
     currentFocus: [
-      { label: "Masters", style: "secondary" },
+      { label: "Master's Research", style: "secondary" },
       { label: "Open Source", style: "accent" },
       { label: "Contract Work", style: "primary" },
     ],

src/content/posts/ascently-climbing-tracker.md

@@ -15,17 +15,17 @@ This seems like a lot more work than its worth. Why would anyone willingly write
 
 **Different platforms are different**
 
-iOS users expect iOS features and design. Material You on Android looks and feels different than iOS's design language, and thats _good_. This is part of what makes these platforms unique. I wanted Ascently to feel hand-crafted for each platform and not like some fully custom design that feels out of place. SwiftUI and Jetpack Compose let me do this while maintaining the declaritive approach I appreciate so much from frameworks like Flutter. I also just genuinely enjoyed learning both frameworks.
+iOS users expect iOS features and design. Material You on Android looks and feels different than iOS's design language, and thats _good_. This is part of what makes these platforms unique. I wanted Ascently to feel hand-crafted for each platform and not like some fully custom design that feels out of place. SwiftUI and Jetpack Compose let me do this while maintaining the declaritive approach I appreciate so much from frameworks like Flutter. I also just genuinely enjoyed learning both platforms.
 
 ## Offline-First
 
-Building Ascently offline-first wasn't a feature... it was a necessity. Your sessions are saved locally and are always accessible. If you want sync, you can run your own lightweight server. But you don't _have_ to. Your data always remains yours, on your device, until you **explicitly** decide otherwise.
+Building Ascently offline-first was front-of-mind from the beginning. Your sessions are saved locally and are always accessible. If you want sync, you can run your own server. But you don't _have_ to. Your data always remains yours, on your device, until you **explicitly** decide otherwise.
 
 ## Privacy as a Feature
 
-No analytics. No tracking. No data collection. I am tired of apps treating privacy like a checkbox to tick instead of a fundamental design choice. I went out of my way to ensure that the ONLY time network calls are made is when you explicitly choose to sync or enable health integration.
+No analytics. No tracking. No data collection. I am tired of apps treating privacy like a checkbox to tick instead of a fundamental design choice. I went out of my way to ensure that the ONLY time network calls are made is when you explicitly choose to sync or enable the health integration.
 
-This made the architecture simpler, honestly. No need to figure out integrating an analytics SDK to integrate. Turns out you don't need to fuss around with building the perfect "privacy respecting analytics" system if you just **don't** collect analytics to begin with.
+This made the architecture simpler. No need to figure out integrating an analytics SDK to integrate. Turns out you don't need to fuss around with building the perfect "privacy respecting analytics" system if you just **don't** collect analytics to begin with.
 
 ## What I've Learned