From 6ab4336a220f61b469b63e1b4e5de9f1c53214d0 Mon Sep 17 00:00:00 2001
From: Debashis Biswas <37234687+debashisbiswas@users.noreply.github.com>
Date: Wed, 13 Dec 2023 11:15:41 -0700
Subject: [PATCH] Fix link to requirements

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 1c93b32b42..f7751eb038 100644
--- a/README.md
+++ b/README.md
@@ -7,7 +7,7 @@ I use this kata as part of my work as a technical coach. I wrote a lot about the
 
 ## How to use this Kata
 
-The simplest way is to just clone the code and start hacking away improving the design. You'll want to look at the ["Gilded Rose Requirements"](https://github.com/emilybache/GildedRose-Refactoring-Kata/blob/main/GildedRoseRequirements.txt) which explains what the code is for. I strongly advise you that you'll also need some tests if you want to make sure you don't break the code while you refactor.
+The simplest way is to just clone the code and start hacking away improving the design. You'll want to look at the ["Gilded Rose Requirements"](https://github.com/emilybache/GildedRose-Refactoring-Kata/blob/main/GildedRoseRequirements.md) which explains what the code is for. I strongly advise you that you'll also need some tests if you want to make sure you don't break the code while you refactor.
 
 You could write some unit tests yourself, using the requirements to identify suitable test cases. I've provided a failing unit test in a popular test framework as a starting point for most languages.