Merge pull request #1586 from SherryHietala/master

Replace 3 instances of "VCS systems" with "VCSs"

Author: ben

book/01-introduction/sections/about-version-control.asc

@@ -44,7 +44,7 @@ However, this setup also has some serious downsides.
 The most obvious is the single point of failure that the centralized server represents.
 If that server goes down for an hour, then during that hour nobody can collaborate at all or save versioned changes to anything they're working on.
 If the hard disk the central database is on becomes corrupted, and proper backups haven't been kept, you lose absolutely everything -- the entire history of the project except whatever single snapshots people happen to have on their local machines.
-Local VCS systems suffer from this same problem -- whenever you have the entire history of the project in a single place, you risk losing everything.
+Local VCSs suffer from this same problem -- whenever you have the entire history of the project in a single place, you risk losing everything.
 
 ==== Distributed Version Control Systems
 

book/02-git-basics/sections/getting-a-repository.asc

@@ -57,7 +57,7 @@ At this point, you have a Git repository with tracked files and an initial commi
 ==== Cloning an Existing Repository
 
 If you want to get a copy of an existing Git repository -- for example, a project you'd like to contribute to -- the command you need is `git clone`.
-If you're familiar with other VCS systems such as Subversion, you'll notice that the command is "clone" and not "checkout".
+If you're familiar with other VCSs such as Subversion, you'll notice that the command is "clone" and not "checkout".
 This is an important distinction -- instead of getting just a working copy, Git receives a full copy of nearly all data that the server has.
 Every version of every file for the history of the project is pulled down by default when you run `git clone`.
 In fact, if your server disk gets corrupted, you can often use nearly any of the clones on any client to set the server back to the state it was in when it was cloned (you may lose some server-side hooks and such, but all the versioned data would be there -- see <<ch04-git-on-the-server#_getting_git_on_a_server>> for more details).

book/02-git-basics/sections/recording-changes.asc

@@ -579,7 +579,7 @@ This command removes all files whose names end with a `~`.
 ==== Moving Files
 
 (((files, moving)))
-Unlike many other VCS systems, Git doesn't explicitly track file movement.
+Unlike many other VCSs, Git doesn't explicitly track file movement.
 If you rename a file in Git, no metadata is stored in Git that tells it you renamed the file.
 However, Git is pretty smart about figuring that out after the fact -- we'll deal with detecting file movement a bit later.