corrections. close SwiftWeekly#5

Author: jessesquires

_posts/2016-01-14-issue-5.md

@@ -31,7 +31,7 @@ Brian Gesiak's "testing the tests" [pull request](https://github.com/apple/swift
 
 ### Proposals
 
-Loïc Lecrenier's [proposal](https://github.com/apple/swift-evolution/blob/master/proposals/0011-replace-typealias-associated.md), *"Replace `typealias` keyword with `associatedtype` for associated type declarations"*, has been [accepted](https://lists.swift.org/pipermail/swift-evolution-announce/2016-January/000014.html) for Swift 2.2! This is a breaking change, but it should be easy to migrate your existing code.
+Loïc Lecrenier's [proposal](https://github.com/apple/swift-evolution/blob/master/proposals/0011-replace-typealias-associated.md), *"Replace `typealias` keyword with `associatedtype` for associated type declarations"*, has been [accepted](https://lists.swift.org/pipermail/swift-evolution-announce/2016-January/000014.html) for Swift 2.2! Using `typealias` in protocols will be deprecated in 2.2 and removed from 3.0 entirely. It should be easy to migrate your existing code.
 
 Doug Gregor [submitted a proposal](https://github.com/apple/swift-evolution/blob/master/proposals/0022-objc-selectors.md), *"Referencing the Objective-C selector of a method"*. It's a dream come true. This has been a glaring issue from the beginning for interoperability with Objective-C. It looks like this feature can be added in Swift 2.2 and deprecate the use of string literals, after which 3.0 would remove the old syntax entirely.
 >*"In Swift 2, Objective-C selectors are written as string literals (e.g., `"insertSubview:aboveSubview:"`) in the type context of a Selector. This proposal seeks to replace this error-prone approach with Selector initialization syntax that refers to a specific method via its Swift name."* 👏