Replace left/right quotation marks

Author: practicalswift

docs/ErrorHandlingRationale.rst

@@ -1359,15 +1359,15 @@ declaration or type::
     return try stream.readInt()
   }
 
-  // ‘throws’ is written before the arrow to give a sensible and
+  // 'throws' is written before the arrow to give a sensible and
   // consistent grammar for function types and implicit () result types.
   func baz() throws {
     if let byte = try stream.getOOB() where byte == PROTO_RESET {
       reset()
     }
   }
 
-  // ‘throws’ appears in a consistent position in function types.
+  // 'throws' appears in a consistent position in function types.
   func fred(callback: (UInt8) throws -> ()) throws {
      while true {
        let code = try stream.readByte()
@@ -1380,7 +1380,7 @@ declaration or type::
   // this function has type:
   //   (Int) -> (Int) throws -> Int
   func jerry(i: Int)(j: Int) throws -> Int {
-    // It’s not an error to use ‘throws’ on a function that can’t throw.
+    // It's not an error to use 'throws' on a function that can't throw.
     return i + j
   }
 

docs/GitWorkflows.rst

@@ -11,7 +11,7 @@ transition to Git this document helps to address questions about how common SVN
 workflows we use today translate to their Git counterparts as well as to discuss
 Git workflow practices we plan on having — at least initially — after the Git
 transition.  Notably we will follow a model where commits to trunk — which is
-the ‘master’ branch in Git — has commits land (in the common case) via rebasing
+the 'master' branch in Git — has commits land (in the common case) via rebasing
 instead of merging.  This model is open to evolution later, but this mimics the
 workflow we have today with SVN.
 

docs/OptimizerDesign.md

@@ -180,7 +180,7 @@ This is an example of the *@_semantics* attribute as used by Swift Array:
 
 Notice that as soon as we inline functions that have the @_semantics attribute
 the attribute is lost and the optimizer can't analyze the content of the
-function. For example, the optimizer can identify the array ‘count' method (that
+function. For example, the optimizer can identify the array 'count' method (that
 returns the size of the array) and can hoist this method out of loops. However,
 as soon as this method is inlined, the code looks to the optimizer like a memory
 read from an undetermined memory location, and the optimizer can't optimize the

docs/proposals/CompressedMangledNames.md

@@ -7,7 +7,7 @@ compiler and make an effort to optimize and shrink the generated binaries. One
 of the problems that we have today is that swift symbols are mangled into
 extremely long strings. This is especially a problem for libraries, and almost
 half of the size of libswiftCore.dylib (the swift runtime library on x86_64 OSX)
-is string tables. On MacOSX you can use the command ’size -m file.dylib’ to read
+is string tables. On MacOSX you can use the command "size -m file.dylib" to read
 the size of the string table. C++ also suffers from the problem of long names,
 but since we control the Swift ABI we can do better than C++.
 
@@ -99,15 +99,15 @@ the top 63 frequent substrings in our dictionary using two characters (escape +
 The second escape character encodes a two-character reference that can access 63 x 63 entries in the table.
 Less common substrings can be encoded using this three character sequence (escape + index0 + index1).
 
-One interesting bit of information is that the character ‘Y’ is only used 4
+One interesting bit of information is that the character "Y" is only used 4
 times in the entire standard library! The letter J, and a few other letters are
 also not used very frequently. We use Y and J as escape characters.
 
 The dictionary-based encoding uses the following rules:
 
 1. We use two escape characters that are not frequently used in names (Y and Z).
 These characters are escape character and cannot be used as part of the text
-without escaping. ‘Y’ is encoded as ‘YY’, and ‘Z’ would be encoded as ‘YZ’.
+without escaping. "Y" is encoded as "YY", and "Z" would be encoded as "YZ".
 
 2. The most commonly used sub-strings (calculated as length of substring times
 number of occurrences) is encoded with a single escape character and a
@@ -216,7 +216,7 @@ Error handling
 The compression routines only handle characters that are in the list of valid
 characters.  It is possible to compress every string that uses the valid
 character set. However, now all incoming strings are legal. For example the
-string "Y" is illegal because 'Y' is an escape character and the decoded expects
+string "Y" is illegal because "Y" is an escape character and the decoded expects
 another character to follow the escape character.
 
 There are a few users that will use the compression routines: The