feat: dev page grammer check

Author: Daniel528

2025/src/components/pages/DevPage.tsx

@@ -1,14 +1,10 @@
-/**
- * Development portfolio page component
- * Modernized version of the original Dev component
- */
 export function DevPage() {
   return (
     <div className="dev" id="primary-content">
       <h1>Software Engineering</h1>
       <p>
         I'm a software engineer who builds interfaces. I'm most familiar with
-        anything under the Javascript umbrella, whether thats in browser,
+        anything under the Javascript umbrella, whether that's in browser,
         desktop native through Electron or mobile native through React Native.
         My most recent work revolves around building React Native applications
         with Typescript and a Redux logic core. I've also written a lot of C#
@@ -20,7 +16,7 @@ export function DevPage() {
         Micromelon Robotics builds a platform for teaching programming, robotics
         and mathematics in schools. I joined Micromelon Robotics on the software
         team and have contributed significantly to the development of all
-        production products. This includes;
+        production products. This includes:
       </p>
       <ul className="key-contributions">
         <li>
@@ -32,7 +28,7 @@ export function DevPage() {
           learning the fundamentals of computational thinking,
         </li>
         <li>
-          Micromelon Toolbox (React Native), a utility app desgined for school
+          Micromelon Toolbox (React Native), a utility app designed for school
           staff to update and manage a class set of Micromelon Rovers
         </li>
         <li>
@@ -44,18 +40,18 @@ export function DevPage() {
 
       <h2>Some Challenges</h2>
       <p>
-        I'll highlight a couple key challenge faced in the last few years when
-        developing with React Native.
+        I'll highlight a couple of key challenges faced in the last few years
+        when developing with React Native.
       </p>
 
       <h3>Async Capable WebView IPC</h3>
       <p>
         The first version of the Code Editor we built was with Electron. However
         a growing number of schools were adopting device policies which had
-        students using Chromebooks or iPads exclusively making it necessary we
-        have an editor which would run on these platforms. We decided to build a
-        mobile compatible Code Editor on React Native. I was one of the key
-        developers involved in this process.
+        students using Chromebooks or iPads exclusively making it necessary that
+        we have an editor which would run on these platforms. We decided to
+        build a mobile compatible Code Editor on React Native. I was one of the
+        key developers involved in this process.
       </p>
       <p>
         Largely the models of Electron and React Native are similar and a port
@@ -85,26 +81,26 @@ export function DevPage() {
       </p>
       <p>
         Once this logic is fulfilled and the original Webview needs a response,
-        our JS thread post office resolves it's promise and sends a sync IPC
+        our JS thread post office resolves its promise and sends a sync IPC
         message to the original Webview. The Promise Post Office in the original
-        webview can cross reference the IPC message with it's unfulfilled
+        webview can cross reference the IPC message with its unfulfilled
         promise, and finally fulfil it with the data it just received.
       </p>
       <p>
         The complexity comes with the nature of the Code Editor having multiple
         webviews to handle each of the coding environments and every thread of
-        python code generating it's own Webview as well as the bluetooth
+        Python code generating its own Webview as well as the bluetooth
         peripherals we connect to.
       </p>
       <p>
-        By far, the most challenging aspect to this was dealing with python
+        By far, the most challenging aspect to this was dealing with Python
         execution in the webview itself. By default, React Native has a single
         JS thread. Hypothetically, a user executing a forever while loop that
         requires IPC messages means the entire JS thread is consumed receiving
-        messages. This issue required it's own solution by with message queues
-        and breathing room delays, I won't get into that here. If you want to
-        hear more about that and how I hate the way Android bundles Webview
-        execution into a single thread, please email me.
+        messages. This issue required its own solution with message queues and
+        breathing room delays, I won't get into that here. If you want to hear
+        more about that and how I hate the way Android bundles Webview execution
+        into a single thread, please email me.
       </p>
       <h3>Accessibility In Micromelon Junior</h3>
       <p>
@@ -116,11 +112,11 @@ export function DevPage() {
         level accessibility feature built into all iOS devices. The majority of
         our app's interface was already accessibility conscious because of React
         Native's built-in accessibility features however a few key buttons were
-        not working with Switch Controls. It was responsible fix this.
+        not working with Switch Controls. I was responsible to fix this.
       </p>
       <p>
         To achieve this, I first had to understand how Switch Control works by
-        configuring it's use on my iPad. I'd encourage anyone to attempt a
+        configuring its use on my iPad. I'd encourage anyone to attempt a
         similar exercise, it's revealing seeing just how difficult it can be to
         interact with an interface which unimpaired users deem to be simple.
         After identifying the problems with Switch Control usage, I refactored
@@ -135,11 +131,11 @@ export function DevPage() {
         Other components we had with swipe interactions were remarkably
         difficult for Switch Control to interface with. To alleviate this, I
         made sure any of these complex components properly implemented props
-        like accessibilityActions to outline it's purpose for Switch Control to
+        like accessibilityActions to outline its purpose for Switch Control to
         read and present directly to the user.
       </p>
       <p>
-        I'm glad to say I was able to make Junior 100% accessibility conscious.
+        I'm glad to say I was able to make Junior 100% accessibility-conscious.
         I'm slightly disheartened I didn't think to check this before the app
         was released. It's unfortunate that it wasn't a front of mind priority
         and equally unfortunate to see how limited some of the React Native