From c9d63cac469b31481c73d97681d03d395c3b790a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Yann=20Sala=C3=BCn?=
 <1910607+yansal@users.noreply.github.com>
Date: Sat, 20 Jan 2024 00:30:37 +0100
Subject: [PATCH] Fix typos in mvc.md (#2208)

---
 www/content/essays/mvc.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/www/content/essays/mvc.md b/www/content/essays/mvc.md
index 47b06cf64..7ab39f43c 100644
--- a/www/content/essays/mvc.md
+++ b/www/content/essays/mvc.md
@@ -87,7 +87,7 @@ def contacts():
     return render_template("index.html", contacts=contacts)
 ```
 
-Here I'm using [Python](https://www.python.org/) and Flask (https://flask.palletsprojects.com/en/3.0.x/), since I use
+Here I'm using [Python](https://www.python.org/) and [Flask](https://flask.palletsprojects.com/en/3.0.x/), since I use
 those in my [Hypermedia Systems](https://hypermedia.systems/) book.
 
 Here you can see that the controller is very "thin": it simply looks up contacts via the `Contact` Model object, passing
@@ -187,7 +187,7 @@ most of the work.
 
 Our two APIs are decoupled, while our domain logic remains centralized.
 
-(Note that this also gets at why [why I tend not to use content negotiation](@/essays/why-tend-not-to-use-content-negotiation.md) and return HTML & JSON from the same endpoint.)
+(Note that this also gets at [why I tend not to use content negotiation](@/essays/why-tend-not-to-use-content-negotiation.md) and return HTML & JSON from the same endpoint.)
 
 ## MVC Frameworks