fix GFM links

Summary.md

@@ -20,7 +20,7 @@ is written in the status reports, not here.*
 
 ::We have completed our second beta release and are currently working on
 adding more of the functionality described in our product
-[specification](srs.html) and fixing defects.
+[specification](SRS) and fixing defects.
 
 ::The next major milestone is a third beta release with nearly complete
 functionality and a wider set of testers.
@@ -33,7 +33,7 @@ functionality and a wider set of testers.
 ### Resources and schedule
 
 *TODO: Briefly describe the project resources and schedule. This is
-condensed from the [project plan](plan.html), [resource needs](resource-needs.html), 
+condensed from the [project plan](Project-Plan), [resource needs](Resource-Needs), 
 and [legal issues](legal.html) documents.*
 
 #### What are the deadlines for this project?
@@ -62,7 +62,7 @@ and [legal issues](legal.html) documents.*
 
 *TODO: Briefly describe the most important system requirements. This is 
 condensed from the [user needs](user-needs.html), 
-[interview notes](interview-notes.html), [SRS](srs.html), 
+[interview notes](interview-notes.html), [SRS](SRS), 
 [use case suite](use-case-suite.html), 
 and [feature set](feature-set.html) documents.*
 
@@ -85,7 +85,7 @@ and [feature set](feature-set.html) documents.*
 ### Design
 
 *TODO: Briefly describe the most important aspects of the design. This is
-condensed from the [design](design.html) template and associated
+condensed from the [design](Design) template and associated
 worksheets.*
 
 #### What are your ranked design goals?
@@ -186,7 +186,7 @@ Where is the user documentation?
 ### Glossary
 *TODO: Define any technical terms that you use above, if a new member of
 the team would not already know them. This is condensed from the
-[glossary](glossary.html) documents.*
+[glossary](Glossary) documents.*
 
 ##### ::TECHNICAL TERM
 ::DEFINITION