fix links, formatting

Author: Fidget-Spinner

README.md

@@ -1,5 +1,3 @@
-# My Personal Blog
-
 Hello! I'm a Python core team member since Aug 2021. I mostly work on the interpreter, JIT compiler's optimizer, and other things in a volunteer capacity. I recently started an actual day job: MPhil/PhD student researching JIT compilers supervised by Laurie Tratt. For open source matters: you can reach me through my email `kenjin@python.org`.
 
 <ul>

_posts/2025-03-08-apology-tail-call.md

@@ -1,7 +1,5 @@
 # I'm Sorry for Python's tail-calling Interpreter's Results
 
-08-Mar-2025
-
 This is my first blog post ever. I want to use it to say
 I'm truly sorry for communicating inaccurate results for
 Python's tail-calling interpreter. I take full personal 

_posts/2025-07-05-jit-reflections.md

@@ -1,7 +1,5 @@
 # Reflections on 2 years of CPython's JIT Compiler: The good, the bad, the ugly
 
-5 July 2025
-
 This blog post includes my honest opinions on the CPython JIT. What I think we did well,
 what I think we could have done better. I'll also do some brief qualititative
 analysis.

_posts/2025-11-08-faster-jit-plan.md

@@ -1,12 +1,10 @@
 # A Plan for 5-10%* Faster Free-Threaded JIT by Python 3.16
 
-08-Nov-2025
-
 During the Python Core Dev Sprint in Cambridge hosted by ARM, we planned to make the JIT in CPython 5% faster by 3.15 and 10% faster by 3.16. The planners present were Savannah Ostrowski, Mark Shannon, Ken Jin (me), Diego Russo and Brandt Bucher. We were accompanied by other CPython core team members as well.
 
 You might wonder: 5% seems awfully conservative. However, note that this figure is the *geometric mean*. The number can range from slower to significantly faster. All numbers are [pyperformance](https://github.com/python/pyperformance) figures.
 
-In my [previous blog post](./jit-reflections.md), I talked about the Python 3.13 and 3.14 JIT's state. We're planning to change that for 3.15 and 3.16.
+In my [previous blog post](./2025-07-05-jit-reflections.md), I talked about the Python 3.13 and 3.14 JIT's state. We're planning to change that for 3.15 and 3.16.
 
 ## The Plan for 3.15
 This is a paraphrase of what Savannah laid out [here](https://github.com/python/cpython/issues/139038). The difference is that I'm listing things in chronological order of what I expect will be merged into CPython.

_posts/2025-12-24-no-longer-sorry.md

@@ -1,8 +1,6 @@
 # Python 3.15's interpreter for Windows x86-64 should hopefully be 15% faster
 
-24 December 2025
-
-Some time ago I posted an [apology piece](./apology-tail-call.md)
+Some time ago I posted an [apology piece](./2025-03-08-apology-tail-call.md)
 for Python's tail calling results. I apologized for communicating performance
 results without noticing a compiler bug had occured.