From 31d2129b8bdc4956a15f2458052711faf6c2c879 Mon Sep 17 00:00:00 2001
From: butteredyakiimo <111829949+butteredyakiimo@users.noreply.github.com>
Date: Wed, 8 Nov 2023 20:03:58 +0800
Subject: [PATCH] Amend planned enhancement

---
 docs/DeveloperGuide.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/DeveloperGuide.md b/docs/DeveloperGuide.md
index f086b6dfe10..0a3919bf6f3 100644
--- a/docs/DeveloperGuide.md
+++ b/docs/DeveloperGuide.md
@@ -411,7 +411,7 @@ command.
 ### Reduce Coupling Between Availability and Animal Type
 Currently, the `animalType` field also contains information about the availability of a fosterer.<br>
 e.g. if the `animalType` field of a fosterer is `able.Dog`, it suggests that the fosterer is available, and is 
-fostering a dog. However, the user will still need to enter the `availability` field as `available`. <br>
+able to foster a dog. However, the user will still need to enter the `availability` field as `available`. <br>
 
 Building on the enhancement in [Shorter Command Formats](#shorter-command-formats), we will be revising the 
 `AVAILABILITY` and `ANIMAL_TYPE` parameters: