Minor typographical modifications, mostly not changing meaning. Feel free to...

Minor typographical modifications, mostly not changing meaning. Feel free to disagree and revert any changes made here.

Proposals/campus-git-1-page-proposal.md

@@ -2,11 +2,11 @@
 
 ## Summary
 
-Today's university environment runs on code. From coursework to administration to research and innovation, a robust version control system (VCS) is the bedrock tool in any software development workflow, and git-based version control is the industry standard[1]. Employers expect new Computer Science graduates to have experience using GitHub[2], a leading cloud-based git service. Our academic peers have incorporated git into their classrooms for years[3] [4]. Campus computing organizations offer git training alongside sessions on campus IT orientation, data management, and popular programming languages[5]. Campus IT Pros use git to manage their codebases, but also as a learning tool, sharing code snippets and suggestions in order to benefit from each other's experience.
+Today's university environment runs on code. From coursework to administration to research and innovation, a robust version control system (VCS) is the bedrock tool in any software development workflow, and git-based version control is the industry standard[1]. Employers expect new Computer Science graduates to have experience using GitHub[2], a leading cloud-based git service. Our academic peers have incorporated git into their classrooms for years[3] [4]. Campus computing organizations offer git training alongside sessions on campus IT orientation, data management, and popular programming languages[5]. Campus IT Pros use git to manage their codebases and also as a learning tool, sharing code snippets and suggestions in order to benefit from each other's experience.
 
-Despite git's ubiquity, the University of Illinois does not offer a campus- or university-level git-based version control service. The closest available option is AITS Subversion[6], which does not support git, nor does it offer the kinds of features commonly found and expected in popular, modern git services[7] [8] [9]. This void has fragmented the campus version control landscape. Though some units do use AITS subversion, many others find this an unsuitable solution. Some units purchase a license and host their own git service, duplicating costs across units; others use cloud-based vendor services, storing university assets offsite; still others, particularly small units and cross-campus affinity groups, simply do without. The net effect is an enormous cost in money, time, and opportunity, with greatly increased business continuity risks.
+Despite git's ubiquity, the University of Illinois does not offer a campus- or university-level git-based version control service. The closest available option is AITS Subversion[6], which does not support git, nor does it offer the kinds of features commonly found and expected in popular, modern git services[7] [8] [9]. This void has fragmented the campus version control landscape. Though some units do use AITS subversion, many others find this an unsuitable solution. Some units purchase a license and host their own git service, duplicating costs across units; others use cloud-based vendor services, storing University assets offsite; still others, particularly small units and cross-campus affinity groups, simply do without. The net effect is an enormous cost in money, time, and opportunity, with substantial business continuity risks.
  
-This document proposes that the University of Illinois launch a campuswide, git-based version control service that supports modern social coding tools, licensed from a reputable vendor. A campus git service would reduce duplicate spending, reduce duplication of effort in both service maintenance and code authoring, and ensure responsible stewardship of university resources, all while encouraging the cross-disciplinary collaboration that is the hallmark of modern software development.
+This document proposes that the University of Illinois launch a campus-wide, git-based version control service that supports modern social coding tools, licensed from a reputable vendor. A campus-wide git service would reduce duplicate spending, reduce duplication of effort in both service maintenance and code authoring, and ensure responsible stewardship of University resources, all while encouraging the cross-disciplinary collaboration that is the hallmark of modern software development.
 
 ## Benefits
 
@@ -16,7 +16,7 @@ Familiarity builds fluency. By providing ready access to mainstream social codin
 
 **Technology for the Good of Campus**
 
-Modern technology requires broad expertise, and social coding services help make non-programmers first-class participants in the development process. A campuswide git-based version control service would ensure that the entire university community has access to today's tools. These services lower the barriers to technical participation, encouraging contributions from all team members and stakeholders, and allowing cross-disciplinary teams to flourish. These services could greatly enhance the experience of our distance learning students, and will be critical for users of campus maker spaces and 3D-printing labs, to say nothing of more traditional users in engineering, computer science, and IT. Today's version control services underpin civic innovation, software development, and everything in between. Our campus users should reflect that trend.
+Modern technology requires broad expertise, and social coding services help make non-programmers first-class participants in the development process. A campus-wide git-based version control service would ensure that the entire university community has access to today's tools. These services lower the barriers to technical participation, encouraging contributions from all team members and stakeholders thereby allowing cross-disciplinary teams to flourish. These services could greatly enhance the experience of our distance learning students, and will be critical for users of campus maker spaces and 3D-printing labs, to say nothing of more traditional users in engineering, computer science, and IT. Today's version control services underpin civic innovation, software development, and everything in between. Our campus users should reflect that trend.
 
 **Teaching and Learning Innovation**
 
@@ -24,11 +24,11 @@ In keeping with social coding's move to the mainstream, service vendors are work
 
 **Research Support**
 
-The university research community needs robust version control and collaboration tools, but is often bound by stringent access control requirements (e.g., HIPAA). We have an opportunity to support research innovation by hosting a storage solution tailored to research needs; combining verifiable data storage practices with easy-to-use, cross-institutional team management and visualization tools[13].
+The University research community needs robust version control and collaboration tools, but is often bound by stringent access control requirements (e.g., HIPAA). We have an opportunity to support research innovation by hosting a storage solution tailored to research needs, combining verifiable data storage practices with easy-to-use, cross-institutional team management and visualization tools[13].
 
 **Administrative Support & Campus Collaborations**
 
-The university could realize immediate administrative support savings by selecting an off-the-shelf appliance from a trusted vendor. Campus units are already licensing and running near-identical services for their own use. By committing to the initial outlay and one-time configuration of a centralized service, we reduce not just the up-front costs of duplication, but the hidden wastes of staff efficiency as well.  
+The University could realize immediate administrative support savings by selecting an off-the-shelf appliance from a trusted vendor. Campus units are already licensing and running near-identical services for their own use. By committing to the initial outlay and one-time configuration of a centralized service, we reduce not just the up-front costs of duplication, but the ongoing hidden wastes of staffing inefficiencies as well.
 
 ## Footnotes