Minor edits

Author: BasThomas

_posts/2017-11-09-issue-94.md

@@ -4,7 +4,7 @@ title: ! 'Issue #94'
 author: modocache
 ---
 
-This week in Swift development: the Swift team created several fun new starter
+This week in Swift development, the Swift team created several fun new starter
 tasks, Doug Gregor fixed a nasty bug in Objective-C interop, and the mailing
 lists were abuzz with several exciting Swift Evolution proposals. Adjust your
 Apple Watches -- it's "Swift Weekly Brief O'Clock"!
@@ -89,7 +89,8 @@ which seems like a good thing to do.
 
 ### Proposals in review
 
-The review of _[SE-0187](https://github.com/apple/swift-evolution/blob/master/proposals/0187-introduce-filtermap.md):
+The [review](https://lists.swift.org/pipermail/swift-evolution-announce/2017-November/000406.html)
+of _[SE-0187](https://github.com/apple/swift-evolution/blob/master/proposals/0187-introduce-filtermap.md):
 Introduce `Sequence.filterMap(_:)`_ has begun and runs through November 14th, 2017.
 
 > We propose to deprecate the controversial version of a `Sequence.flatMap`
@@ -99,7 +100,8 @@ Introduce `Sequence.filterMap(_:)`_ has begun and runs through November 14th, 20
   still be available (although deprecated) all the existing code will compile,
   producing a deprecation warning and a fix-it.
 
-The review of _[SE-0188](https://github.com/apple/swift-evolution/blob/master/proposals/0188-stdlib-index-types-hashable.md):
+The [review](https://lists.swift.org/pipermail/swift-evolution-announce/2017-November/000407.html)
+of _[SE-0188](https://github.com/apple/swift-evolution/blob/master/proposals/0188-stdlib-index-types-hashable.md):
 Make stdlib index types `Hashable`_ begins now and runs through November 14th, 2017.
 
 > This proposal would add `Hashable` conformance to all the index types in the
@@ -143,7 +145,7 @@ condition. Replies to the proposal began to discuss what attributes should be
 available as platform conditions. This week, Graydon [pointed out](https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20171030/040819.html)
 that whether the compilation target was a simulator or not was encoded in the
 target triple, a decision made recently in LLVM, so discussions of whether it
-should be encoded at all should be done on LLVM mailing lists.
+should be encoded at all should be done on the LLVM mailing lists.
 
 [Brent Royal-Gordon](https://twitter.com/brentdax) [asked](https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20171030/040863.html)
 about how he could update his once deferred proposal, [SE-0132](https://github.com/apple/swift-evolution/blob/master/proposals/0132-sequence-end-ops.md),