From ea1fa29db72274b5cfb0033cdd69401864f30899 Mon Sep 17 00:00:00 2001
From: "Tyrrell, Megan R (UG - Comp Sci & Elec Eng)" <mt01317@surrey.ac.uk>
Date: Fri, 9 Feb 2024 11:47:14 +0000
Subject: [PATCH] Update README.md

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

diff --git a/README.md b/README.md
index 0bfeaae..b279db3 100644
--- a/README.md
+++ b/README.md
@@ -53,7 +53,7 @@ When you're ready to make this README your own, just edit this file and use the
 Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
 
 ## Name
-Choose a self-explaining name for your project.
+TestVisibility
 
 ## Description
 Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-- 
GitLab