Update the URLs from apple/swift-evolution to swiftlang/swift-evoluti…

…on (swiftlang#714)

_posts/2015-12-03-swift-3-api-design.md

@@ -67,10 +67,10 @@ repository][swift-3-api-guidelines-repo], then join the discussion on
 the [swift-evolution mailing
 list](/community/#swift-evolution).
 
-[swift-3-goals]: https://github.com/apple/swift-evolution/blob/master/README.md  "Swift 3 goals"
+[swift-3-goals]: https://github.com/swiftlang/swift-evolution/blob/master/README.md  "Swift 3 goals"
 [swift-api-guidelines]: /documentation/api-design-guidelines/  "Swift API Design Guidelines"
 [swift-stdlib-update]: https://github.com/apple/swift/tree/swift-3-api-guidelines  "Swift 3 Standard Library updates"
-[clang-importer-proposal]: https://github.com/apple/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md  "Better Translation of Objective-C APIs into Swift proposal"
+[clang-importer-proposal]: https://github.com/swiftlang/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md  "Better Translation of Objective-C APIs into Swift proposal"
 [swift-3-api-guidelines-repo]: https://github.com/apple/swift-3-api-guidelines-review  "Swift 3 API Design Guidelines review repository"
 [objc-cocoa-guidelines]: https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/CodingGuidelines/CodingGuidelines.html  "Objective-C Coding Guidelines for Cocoa"
 [swift-evolution]: /contributing/#evolution-process  "Swift evolution process"

_posts/2016-01-29-swift-api-transformation.md

@@ -60,10 +60,10 @@ path.fillWith(kCGBlendModeMultiply, alpha: 0.7)
 
 We've put three parts of this proposed transformation up for public
 review in [Swift's evolution group](/community/#mailing-lists):
-[changes to how Cocoa is imported](https://github.com/apple/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md),
-[changes to the surface of the standard library](https://github.com/apple/swift-evolution/blob/master/proposals/0006-apply-api-guidelines-to-the-standard-library.md),
+[changes to how Cocoa is imported](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md),
+[changes to the surface of the standard library](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0006-apply-api-guidelines-to-the-standard-library.md),
 and the
-[API guidelines](https://github.com/apple/swift-evolution/blob/master/proposals/0023-api-guidelines.md)
+[API guidelines](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0023-api-guidelines.md)
 that tie this all together. Suggestions for improvement have already
 started coming in
 from participants, and we're able to see how they
@@ -96,7 +96,7 @@ language and frameworks,
 [join the discussion](/contributing/#participating-in-the-swift-evolution-process).
 The proposals and associated review threads are here:
 
-* [API Design Guidelines](https://github.com/apple/swift-evolution/blob/master/proposals/0023-api-guidelines.md) — [discussion](http://news.gmane.org/find-root.php?message_id=ABB71FFD%2d1AE8%2d43D3%2dB3F5%2d58225A2BAD66%40apple.com)
-* [Better Translation of Objective-C APIs Into Swift](https://github.com/apple/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md) — [discussion](http://news.gmane.org/find-root.php?message_id=CC036592%2d085D%2d4095%2d8D73%2d1DA9FC90A07B%40apple.com)
-* [Apply API Guidelines to the Standard Library](https://github.com/apple/swift-evolution/blob/master/proposals/0006-apply-api-guidelines-to-the-standard-library.md) — [discussion](http://news.gmane.org/find-root.php?message_id=73E699B0%2dFAD2%2d46DA%2dB74E%2d849445A2F38A%40apple.com)
+* [API Design Guidelines](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0023-api-guidelines.md) — [discussion](http://news.gmane.org/find-root.php?message_id=ABB71FFD%2d1AE8%2d43D3%2dB3F5%2d58225A2BAD66%40apple.com)
+* [Better Translation of Objective-C APIs Into Swift](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md) — [discussion](http://news.gmane.org/find-root.php?message_id=CC036592%2d085D%2d4095%2d8D73%2d1DA9FC90A07B%40apple.com)
+* [Apply API Guidelines to the Standard Library](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0006-apply-api-guidelines-to-the-standard-library.md) — [discussion](http://news.gmane.org/find-root.php?message_id=73E699B0%2dFAD2%2d46DA%2dB74E%2d849445A2F38A%40apple.com)
 

_posts/2016-03-21-swift-2.2-released.md

@@ -12,13 +12,13 @@ We are very pleased to announce the release of Swift 2.2!  This is the first off
 
 Swift 2.2 is a minor language release that is mostly source-compatible with Swift 2.1.  It contains the following language changes that went through the Swift's [evolution process](/contributing/#participating-in-the-swift-evolution-process):
 
-* [SE-0001: Allow (most) keywords as argument labels](https://github.com/apple/swift-evolution/blob/master/proposals/0001-keywords-as-argument-labels.md)
-* [SE-0015: Tuple comparison operators](https://github.com/apple/swift-evolution/blob/master/proposals/0015-tuple-comparison-operators.md)
-* [SE-0014: Constraining `AnySequence.init`](https://github.com/apple/swift-evolution/blob/master/proposals/0014-constrained-AnySequence.md)
-* [SE-0011: Replace `typealias` keyword with `associatedtype` for associated type declarations](https://github.com/apple/swift-evolution/blob/master/proposals/0011-replace-typealias-associated.md)
-* [SE-0021: Naming Functions with Argument Labels](https://github.com/apple/swift-evolution/blob/master/proposals/0021-generalized-naming.md)
-* [SE-0022: Referencing the Objective-C selector of a method](https://github.com/apple/swift-evolution/blob/master/proposals/0022-objc-selectors.md)
-* [SE-0020: Swift Language Version Build Configuration](https://github.com/apple/swift-evolution/blob/master/proposals/0020-if-swift-version.md)
+* [SE-0001: Allow (most) keywords as argument labels](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0001-keywords-as-argument-labels.md)
+* [SE-0015: Tuple comparison operators](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0015-tuple-comparison-operators.md)
+* [SE-0014: Constraining `AnySequence.init`](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0014-constrained-AnySequence.md)
+* [SE-0011: Replace `typealias` keyword with `associatedtype` for associated type declarations](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0011-replace-typealias-associated.md)
+* [SE-0021: Naming Functions with Argument Labels](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0021-generalized-naming.md)
+* [SE-0022: Referencing the Objective-C selector of a method](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0022-objc-selectors.md)
+* [SE-0020: Swift Language Version Build Configuration](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0020-if-swift-version.md)
 
 Beyond these language changes Swift 2.2 also contains numerous bug fixes, enhancements to diagnostics, and produces even faster-running code.
 

_posts/2016-03-30-swift-2.2-new-features.md

@@ -40,7 +40,7 @@ As long as the Swift compiler targets 3.0 or greater, that will compile just fin
 
 A word of warning: this feature is not useable at this time, because a Swift 2.1 compiler will choke on `#if swift(>=2.2)` — it has no idea what that means. However, once Swift 3.0 becomes available, and for all future versions, compile-time Swift version checks will be a useful addition to your toolkit.
 
-For more information, see the [Swift Evolution proposal](https://github.com/apple/swift-evolution/blob/master/proposals/0020-if-swift-version.md) for this change.
+For more information, see the [Swift Evolution proposal](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0020-if-swift-version.md) for this change.
 
 ### Compile-time checked selectors
 
@@ -82,7 +82,7 @@ func addNewFireflyReference() {
 
 When that code is built, the compiler will send back the error "Use of unresolved identifier 'addNewFireflyRefernce'" — shiny!
 
-For more information, see the [Swift Evolution proposal](https://github.com/apple/swift-evolution/blob/master/proposals/0022-objc-selectors.md) or read the [swift-evolution-announce post](https://lists.swift.org/pipermail/swift-evolution-announce/2016-January/000026.html) detailing the rationale.
+For more information, see the [Swift Evolution proposal](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0022-objc-selectors.md) or read the [swift-evolution-announce post](https://lists.swift.org/pipermail/swift-evolution-announce/2016-January/000026.html) detailing the rationale.
 
 ### More keywords as argument labels
 
@@ -106,7 +106,7 @@ func visitCity(name: String, in state: String) {
 visitCity("Nashville", in: "Tennessee")
 ~~~
 
-For more information, see the [Swift Evolution proposal](https://github.com/apple/swift-evolution/blob/master/proposals/0001-keywords-as-argument-labels.md) for this change.
+For more information, see the [Swift Evolution proposal](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0001-keywords-as-argument-labels.md) for this change.
 
 ### Tuple comparison is built-in
 
@@ -140,7 +140,7 @@ if singer == bird {
 }
 ~~~
 
-For more information, see the [Swift Evolution proposal](https://github.com/apple/swift-evolution/blob/master/proposals/0015-tuple-comparison-operators.md) for this change.
+For more information, see the [Swift Evolution proposal](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0015-tuple-comparison-operators.md) for this change.
 
 ### Tuple splat syntax is deprecated
 
@@ -157,7 +157,7 @@ describePerson(person)
 
 This syntax — affectionately called "tuple splat syntax" — is the antithesis of idiomatic Swift's self-documenting, readable style, and so it's deprecated in Swift 2.2.
 
-For more information, see the [Swift Evolution proposal](https://github.com/apple/swift-evolution/blob/master/proposals/0029-remove-implicit-tuple-splat.md) or read the [swift-evolution-announce post](https://lists.swift.org/pipermail/swift-evolution-announce/2016-February/000033.html) detailing the rationale.
+For more information, see the [Swift Evolution proposal](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0029-remove-implicit-tuple-splat.md) or read the [swift-evolution-announce post](https://lists.swift.org/pipermail/swift-evolution-announce/2016-February/000033.html) detailing the rationale.
 
 ### C-style `for` loops are deprecated
 
@@ -203,7 +203,7 @@ for i in 0.stride(to: 10, by: 2) {
 }
 ~~~
 
-For more information, see the [Swift Evolution proposal](https://github.com/apple/swift-evolution/blob/master/proposals/0007-remove-c-style-for-loops.md) or read the [swift-evolution-announce post](https://lists.swift.org/pipermail/swift-evolution-announce/2015-December/000001.html) detailing the rationale.
+For more information, see the [Swift Evolution proposal](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0007-remove-c-style-for-loops.md) or read the [swift-evolution-announce post](https://lists.swift.org/pipermail/swift-evolution-announce/2015-December/000001.html) detailing the rationale.
 
 ### `++` and `--` are deprecated
 
@@ -228,9 +228,9 @@ There is no single reason for this change. Instead, it's a number of small reaso
 * C-style loops — a common place where `++` and `--` are used — are also being deprecated.
 * Using the result of these operators depends on whether they are used prefix or postfix, which can cause confusion.
 
-There's a quote in the Swift Evolution proposal for this change that sums up the rationale concisely: these fail the metric of "if we didn't already have these, would we add them to Swift 3?" \[[1](https://github.com/apple/swift-evolution/blob/master/proposals/0004-remove-pre-post-inc-decrement.md)\]
+There's a quote in the Swift Evolution proposal for this change that sums up the rationale concisely: these fail the metric of "if we didn't already have these, would we add them to Swift 3?" \[[1](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0004-remove-pre-post-inc-decrement.md)\]
 
-For more information, see the [Swift Evolution proposal](https://github.com/apple/swift-evolution/blob/master/proposals/0004-remove-pre-post-inc-decrement.md) for this change.
+For more information, see the [Swift Evolution proposal](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0004-remove-pre-post-inc-decrement.md) for this change.
 
 ### `var` parameters are deprecated
 
@@ -271,11 +271,11 @@ func greet(name: String) {
 }
 ~~~
 
-For more information, see the [Swift Evolution proposal](https://github.com/apple/swift-evolution/blob/master/proposals/0003-remove-var-parameters.md) or read the [swift-evolution-announce post](https://lists.swift.org/pipermail/swift-evolution-announce/2016-January/000027.html) detailing the rationale.
+For more information, see the [Swift Evolution proposal](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0003-remove-var-parameters.md) or read the [swift-evolution-announce post](https://lists.swift.org/pipermail/swift-evolution-announce/2016-January/000027.html) detailing the rationale.
 
 ### Renamed debug identifiers
 
-The Swift compiler automatically provides some symbols that are useful when debugging. Previously these were in "screaming snake case", so `__FILE__` would be replaced with the name of the current Swift file, `__LINE__` with the line number and so on. In Swift 2.2 those old identifiers are deprecated and replaced with `#file`, `#line`, `#column`, and `#function`, which introduces "a convention where # means invoke compiler substitution logic here." \[[2](https://github.com/apple/swift-evolution/blob/master/proposals/0028-modernizing-debug-identifiers.md)\]
+The Swift compiler automatically provides some symbols that are useful when debugging. Previously these were in "screaming snake case", so `__FILE__` would be replaced with the name of the current Swift file, `__LINE__` with the line number and so on. In Swift 2.2 those old identifiers are deprecated and replaced with `#file`, `#line`, `#column`, and `#function`, which introduces "a convention where # means invoke compiler substitution logic here." \[[2](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0028-modernizing-debug-identifiers.md)\]
 
 Here's an example demonstrating the old and new syntax:
 
@@ -293,7 +293,7 @@ func visitCity(name: String, in state: String) {
 
 As with many other changes, Xcode has a Fix-it that will update your code correctly.
 
-For more information, see the [Swift Evolution proposal](https://github.com/apple/swift-evolution/blob/master/proposals/0028-modernizing-debug-identifiers.md) or read the [swift-evolution-announce post](https://lists.swift.org/pipermail/swift-evolution-announce/2016-February/000030.html) detailing the rationale.
+For more information, see the [Swift Evolution proposal](https://github.com/swiftlang/swift-evolution/blob/master/proposals/0028-modernizing-debug-identifiers.md) or read the [swift-evolution-announce post](https://lists.swift.org/pipermail/swift-evolution-announce/2016-February/000030.html) detailing the rationale.
 
 
 ### And there's more…

_posts/2016-05-06-swift-3.0-release-process.md

@@ -13,7 +13,7 @@ Swift 3.0 is a major release that is *not* source-compatible with Swift 2.2. It
 contains fundamental changes to the language and Swift Standard Library.  A
 comprehensive list of implemented changes for Swift 3.0 can be found on the
 [Swift evolution
-site](https://github.com/apple/swift-evolution#implemented-proposals-for-swift-3).
+site](https://github.com/swiftlang/swift-evolution#implemented-proposals-for-swift-3).
 
 Swift 3.0 is also the first release to include the [Swift Package Manager](/documentation/package-manager/).  While the Swift Package Manager is still early
 in its development, it supports the development and distribution of
@@ -71,7 +71,7 @@ Swift.org release, Swift 3.0 will ship in a future version of Xcode.
   considered on a case-by-case basis.
 
 - All language and API changes for Swift 3.0 will go through the [Swift
-  Evolution](https://github.com/apple/swift-evolution) process.
+  Evolution](https://github.com/swiftlang/swift-evolution) process.
 
 - Criteria — as set by the release manager — for accepting changes
   will becoming increasingly restrictive over time as the release