fix: Reformatted

Author: dbrattli

.markdownlint.json

@@ -1,5 +1,6 @@
 {
   "MD013": false,
   "MD024": false,
-  "MD033": false
+  "MD033": false,
+  "MD051": false
 }

Fable.Literate/App.fs

@@ -464,6 +464,6 @@ dotnet fable Fable.Literate/ --lang python -o output/Fable.Literate/
 python output/Fable.Literate/app.py chapters/introduction.fs > docs/introduction.md
 ```
 
-That's it! A complete literate programming converter in under 200 lines of F`#`,
+That's it! A complete literate programming converter in under 200 lines of F#,
 compiled to Python, processing this very blog post.
 *)

chapters/AsyncProgramming.fs

@@ -32,7 +32,7 @@ F# provides two computation expressions that compile to Python's async model:
 - **`async { }`** - F#'s original async workflows (cold, composable, multi-target)
 - **`task { }`** - .NET-style tasks (hot in .NET, compiles to native `async def` in Python)
 
-## F`#` Async Workflows
+## F# Async Workflows
 
 The `async` computation expression has been part of F# since the beginning. It creates
 *cold* async operations - they don't start until explicitly run.

chapters/GettingStarted.fs

@@ -37,7 +37,7 @@ dotnet add package Fable.Core --version 5.0.0-beta.4
 Fable-generated Python code requires the `fable-library` runtime:
 
 ```bash
-pip install "fable-library==5.0.0a20"
+pip install "fable-library==5.0.0a21"
 ```
 
 ---

chapters/Introduction.fs

@@ -10,6 +10,24 @@ this wonderful tradition that brings the F# community together every year!
 Welcome to this guide on [Fable.Python](https://github.com/fable-compiler/Fable.Python/) -
 a compiler that transforms F# code into Python.
 
+## Table of Contents
+
+1. [F# for Python Developers](#heading-are-you-a-python-developer) - Core concepts if you're coming from Python
+2. [Getting Started](#heading-getting-started-with-fablepython) - Installation and your first project
+3. [Python Interop](#heading-python-interop) - Calling Python libraries from F#
+4. [Creating Bindings](#heading-creating-python-bindings) - Type-safe wrappers for Python packages
+5. [F# Compatibility](#heading-f-compatibility-in-fablepython) - What works, what doesn't
+6. [Async Programming](#heading-async-programming) - F# async and Python asyncio
+7. [Testing](#heading-testing-fablepython-projects) - Using pytest with F# code
+8. [Fable v5](#heading-fable-v5-whats-new) - New features and the Rust core
+9. [Pydantic Integration](#heading-pydantic-interop) - Type-safe data validation
+10. [Units of Measure](#heading-units-of-measure) - Compile-time dimensional analysis
+11. [Fable.Literate](#heading-fableliterate-the-strange-loop) - The tool that wrote this post
+
+**A teaser:** the final chapter reveals how this entire blog post was generated. The converter that transforms F#
+literate files into Markdown is itself written in F#, compiled to Python with Fable, and documented using its own
+output format. It's turtles all the way down.
+
 ## What is Fable?
 
 [Fable](https://fable.io/) is a compiler that brings F# to different platforms and ecosystems. While
@@ -100,7 +118,5 @@ shape variant, the compiler will warn you about unhandled cases in the `area` fu
 ## What's Next?
 
 In the following chapters, we'll explore setting up your environment, working with Python libraries, and understanding
-F# compatibility with Fable.
-
-Let's begin.
+F# compatibility with Fable. Let's begin.
 *)

chapters/Summary.fs

@@ -7,13 +7,13 @@ module Summary
 We've covered a lot of ground in this guide:
 
 - **Introduction**: What Fable.Python is and why it matters
-- **F`#` for Python Developers**: Bridging the conceptual gap between languages
+- **F# for Python Developers**: Bridging the conceptual gap between languages
 - **Getting Started**: Setting up your first Fable.Python project
-- **Interop**: Seamlessly calling Python libraries from F`#`
+- **Interop**: Seamlessly calling Python libraries from F#
 - **Bindings**: Creating type-safe wrappers for Python code
-- **Compatibility**: Understanding what F`#` features work (and which don't)
-- **Async Programming**: Mapping F`#` async to Python's asyncio
-- **Testing**: Running F`#` code with pytest and other Python test runners
+- **Compatibility**: Understanding what F# features work (and which don't)
+- **Async Programming**: Mapping F# async to Python's asyncio
+- **Testing**: Running F# code with pytest and other Python test runners
 - **Fable v5**: The latest features including the Rust core and PyPI packages
 - **Pydantic**: Building validated data models with Python's favorite library
 - **Units of Measure**: Compile-time dimensional analysis that vanishes at runtime
@@ -24,7 +24,7 @@ We've covered a lot of ground in this guide:
 If you're reading this, the code worked.
 
 This entire blog post - every chapter, every code example, every explanation -
-was processed by F`#` code compiled to Python, and output as Markdown.
+was processed by F# code compiled to Python, and output as Markdown.
 The proof is in the reading.
 
 ## Get Involved
@@ -34,7 +34,7 @@ The source code for this entire project is available on GitHub:
 **[github.com/cardamomcode/fable-python](https://github.com/cardamomcode/fable-python)**
 
 The repository contains:
-- All the chapter source files (literate F`#`)
+- All the chapter source files (literate F#)
 - The Fable.Literate converter
 - Build scripts and configuration
 - The generated blog post
@@ -47,8 +47,7 @@ from the community make it better for everyone.
 
 - [Fable Documentation](https://fable.io/docs/)
 - [Fable.Python on GitHub](https://github.com/fable-compiler/Fable.Python/)
-- [F`#` Software Foundation](https://fsharp.org/)
-- [Fable Discord](https://discord.gg/8c3Ng9N) - The Fable community is friendly and helpful
+- [F# Software Foundation](https://fsharp.org/)
 
 Welcome to Fable.Python. Now go build something.
 *)