reword and fix broken stuff

src/components/BlogPreview.astro

@@ -74,7 +74,7 @@ const { pubDate, title, description, url, colorDotRed, first, last } =
 
     .description {
       word-wrap: break-word;
-      row-start: 3;
+      grid-row-start: 3;
       grid-column-start: 5;
       color: hsl(0, 0%, 65%);
     }

src/content/config.ts

@@ -75,7 +75,7 @@ const cubingCompetitionCollection = defineCollection({
     slugOverride: z.string().optional(),
     results: z.array(
       z.object({
-        round: z.union([z.literal("SEMI-FINALS"), z.literal("FINALS"), z.number()]),
+        round: z.union([z.literal("Semi-finals"), z.literal("Finals"), z.number()]),
         place: z.number().int(),
         times: z.array(z.union([z.literal("DNF"), z.number()])).length(5),
         plusTwos: z.array(z.number().int()).max(5).optional(),

src/pages/cubing.astro

@@ -50,10 +50,9 @@ const cubingCompetitions = await getCollection("cubing-competition");
     />
     <p>
       Fancy, I know right? When I got this cube in particular, I started an
-      experiment and adjusted the tensioning towards the faster setting. I
-      noticed in my previous Rubik's cube mains that I would always adjust the
-      tension towards the slower end because applied too much force while
-      turning, tiring me out.
+      experiment and adjusted the tensioning towards the faster end. In the
+      past, I always adjusted the tension towards the slower end because I would
+      apply too much force while turning and tire me out.
     </p>
     <p>
       Although it was hard getting used to at first, so far I think the
@@ -62,11 +61,10 @@ const cubingCompetitions = await getCollection("cubing-competition");
     </p>
     <h2>Personal Best Solve</h2>
     <p>
-      This solve is one-of-a-kind; at the time of writing, no other solve of
-      mine comes close to how extraordinary this one is. For perspective, from
-      around ten thousand prior career solves, my previous personal best was
-      8.62 seconds. It was my most dramatic personal best solve time jump, and
-      no other solve time other than <a
+      This solve is one-of-a-kind. For perspective, from around ten thousand
+      prior career solves, my previous personal best was 8.62 seconds. It was my
+      most dramatic personal best solve time jump, and no other solve time other
+      than <a
         href="https://alg.cubing.net/?type=reconstruction&setup=B-_R_D2_L-_F2_L-_U2_F2_L-_F2_R-_F2_B-_L-_R2_D-_R-_F_L-&alg=x2_y_%2F%2F_Inspection%0AD-_R-_D2_F_B-_R_D2_%2F%2F_Cross%0AL-_U_L_y-_R-_U2_R_%2F%2F_1st_Pair%0AL_F-_L-_F_L_U_L-_%2F%2F_2nd_Pair%0Ay-_U_R-_U-_R_%2F%2F_3rd_Pair%0AU_R_U_R-_%2F%2F_4th_Pair%0Af_R_U_R-_U-_f-_U-_R_U_R-_U-_R-_F_R_F-_%2F%2F_OLL%0A%0A%2F%2F_Solved_on_Dec_5,_2022&title=Arhan%20Chaudhary,%206.82%20seconds&view=playback"
         >this contender</a
       > has come close after more than five years. Without further ado:
@@ -104,23 +102,22 @@ const cubingCompetitions = await getCollection("cubing-competition");
       > if needed.
     </p>
     <p>
-      Before you've even picked up the cube, you can already tell that the solve
-      presents a special opportunity. There exists not one, but <i>two</i> completed
-      2x2x1 F2L blocks. Complemented by easy cross edges, the solve manifests a rare
-      XXCross! Following that, the third and fourth pairs were easy-to-look-ahead
-      2-gen algorithms that each required a rotation for setup.
+      Before picking up the cube, you can already tell that the solve presents a
+      special opportunity. There exists not one, but <i>two</i> completed 2x2x1 F2L
+      blocks. Complemented by easy edges, the solve manifests a rare XX Cross! Following
+      that, the third and fourth pairs were easy-to-look-ahead 2-gen algorithms that
+      each required a rotation for setup.
     </p>
     <p>
-      I couldn't have asked for an easier OLL; the fat anti-sune is one of my
-      fastest algorithms. Plus, it was already U-face oriented, making for easy
-      recognition. On the other hand, I was met with a Ja PLL, an algorithm I've
-      historically locked up on. Surprisingly, my execution was flawless, aided
-      by 25% chance of no AUF. Given that I've always struggled with solve
-      anxiety especially towards the end of the solve, I can't help but give
-      myself a pat on the back for how elegant the last layer was. Through the
-      culmination of an awesome scramble and perhaps an even more awesome
-      solution, my 6.48 second Rubik's cube solve is forever cemented as one of
-      my proudest life accomplishments!
+      I couldn't have asked for a better last layer. The fat anti-sune, already
+      U-face oriented, is one of my fastest OLL algorithms. On the other hand, I
+      was met with a Ja PLL, an algorithm I've historically locked up on. My
+      execution was flawless and aided by the 25% chance of no AUF. Given that
+      I've always struggled with solve anxiety especially towards the end of the
+      solve, I can't help but give myself a pat on the back for how elegant the
+      last layer was. Through the culmination of an awesome scramble and perhaps
+      an even more awesome solution, my 6.48 second Rubik's cube solve is
+      forever cemented as one of my proudest life accomplishments!
     </p>
     <h2>My Competitions</h2>
     {

src/pages/projects.astro

@@ -51,7 +51,7 @@ import Project from "../components/Project.astro";
         GitHub users and add them as contributors to the repo.
       </p>
       <p>
-        <a href="https://github.com/ArhanChaudhary/TimeWeb">GitHub repository</a
+        <a href="https://github.com/ArhanChaudhary/everyone">GitHub repository</a
         >
       </p>
     </Project>