From 00605b2bfec4439c1a2ae05b03f1565dfe7deae4 Mon Sep 17 00:00:00 2001
From: Andrew Reynolds <areynold@illinois.edu>
Date: Fri, 20 Jan 2017 12:11:52 -0600
Subject: [PATCH] clarify readme

---
 README.md | 50 +++++++++++++++++++++++++-------------------------
 1 file changed, 25 insertions(+), 25 deletions(-)

diff --git a/README.md b/README.md
index 3e66ece..f5f7d8b 100644
--- a/README.md
+++ b/README.md
@@ -1,25 +1,25 @@
-# Pilot Service Use Cases & User Stories
-
-This project contains use cases, user stories, and related documents for the practical evaluation of pilot service candidates.
-
-See the [Contribution Guide](CONTRIBUTING.md) for information on using these projects, or contact <git-pilot-participants@mx.uillinois.edu>.
-
-Pilot Committee meeting notes and project status can be found in the [Git Committee Notes](https://gitlab-beta.engr.illinois.edu/git-solutions-committee/git-committee-notes) project.
-
-## Project Structure
-
-### Resources
-
-Service documentation, migration guides, and links to external resources. Files arranged by topic.
-
-### Use Cases
-
-Formal descriptions of features or requirements and their evaluation criteria, beginning with a user story. Templates are available in the Template subdirectory.
-
-One use case per file.
-
-### User Stories
-
-Anecdotal service requirements. At minimum, each user story should contain a subject and action. User stories should contain a success indicator and rationale. If the level of need is known, user stories may use the MoSCoW scale (i.e., Must, Should, Could, Won't) as a general indicator.
-
-User stories are arranged topically by file, with each file containing several subcategories, and each subcategory containing one or more user story.
+# Git Service Use Cases & User Stories
+
+This project contains use cases, user stories, and related documents for the practical evaluation of service candidates.
+
+See the [Contribution Guide](CONTRIBUTING.md) for information on using these projects.
+
+Committee meeting notes and project status can be found in the [Git Committee Notes](https://gitlab-beta.engr.illinois.edu/git-solutions-committee/git-committee-notes) project.
+
+## Project Structure
+
+### Resources
+
+Service documentation, migration guides, and links to external resources. Files arranged by topic.
+
+### Use Cases
+
+Formal descriptions of features or requirements and their evaluation criteria, beginning with a user story. Templates are available in the Template subdirectory.
+
+One use case per file.
+
+### User Stories
+
+Anecdotal service requirements. At minimum, each user story should contain a subject and action. User stories should contain a success indicator and rationale. If the level of need is known, user stories may use the MoSCoW scale (i.e., Must, Should, Could, Won't) as a general indicator.
+
+User stories are arranged topically by file, with each file containing several subcategories, and each subcategory containing one or more user story.
-- 
GitLab