Simple standardization of " -- " for em dashes in "Distributed Workflows"

Author: robertpjday

book/05-distributed-git/sections/distributed-workflows.asc

@@ -3,16 +3,16 @@
 (((workflows)))
 Unlike Centralized Version Control Systems (CVCSs), the distributed nature of Git allows you to be far more flexible in how developers collaborate on projects.
 In centralized systems, every developer is a node working more or less equally on a central hub.
-In Git, however, every developer is potentially both a node and a hub – that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to.
+In Git, however, every developer is potentially both a node and a hub -- that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to.
 This opens a vast range of workflow possibilities for your project and/or your team, so we'll cover a few common paradigms that take advantage of this flexibility.
 We'll go over the strengths and possible weaknesses of each design; you can choose a single one to use, or you can mix and match features from each.
 
 ==== Centralized Workflow
 
 (((workflows, centralized)))
-In centralized systems, there is generally a single collaboration model – the centralized workflow.
+In centralized systems, there is generally a single collaboration model -- the centralized workflow.
 One central hub, or _repository_, can accept code, and everyone synchronizes their work to it.
-A number of developers are nodes – consumers of that hub – and synchronize to that one place.
+A number of developers are nodes -- consumers of that hub -- and synchronize to that one place.
 
 .Centralized workflow.
 image::images/centralized_workflow.png[Centralized workflow.]
@@ -57,7 +57,7 @@ image::images/integration-manager.png[Integration-manager workflow.]
 (((forking)))
 This is a very common workflow with hub-based tools like GitHub or GitLab, where it's easy to fork a project and push your changes into your fork for everyone to see.
 One of the main advantages of this approach is that you can continue to work, and the maintainer of the main repository can pull in your changes at any time.
-Contributors don't have to wait for the project to incorporate their changes – each party can work at their own pace.
+Contributors don't have to wait for the project to incorporate their changes -- each party can work at their own pace.
 
 ==== Dictator and Lieutenants Workflow