Merge pull request #75 from MattWis/patch-1

Grammar pass

Author: jamesmunns

newsletters/2018-03-29.md

@@ -157,7 +157,7 @@ This feature has been proposed for stabilization (cf. [rust-lang/rust#24111]).
 
 **Background**: Some assembly operations can be implemented as external assembly files that are then called into using FFI; other ops though do need to be inlined into the function from which they are called to prevent losing semantics. Using external assembly file can be done on the stable channel. The second type of operation requires the unstable `asm!` macro.
 
-The compiler team is not 100% sure on whether they want to stabilize inline assembly for the edition release. The embedded WG has proposed an alternative proposal: expose *some* assembly operations that need to be inlined as "Rust intrinsics" -- in a similar fashion to how SIMD is being implemented; these intrinsics would be in the `core::asm::$ARCH` module and they could either be implemented by lowering to a LLVM intrinsics or using inline assembly. For example:
+The compiler team is not 100% sure on whether they want to stabilize inline assembly for the edition release. The embedded WG has proposed an alternative proposal: expose *some* assembly operations that need to be inlined as "Rust intrinsics" -- in a similar fashion to how SIMD is being implemented; these intrinsics would be in the `core::asm::$ARCH` module and they could either be implemented by lowering to a LLVM intrinsic or using inline assembly. For example:
 
 ``` rust
 pub mod asm {
@@ -172,13 +172,13 @@ pub mod asm {
 }
 ```
 
-These would be stable APIs with an unstable implementation. If LLVM assembler syntax the implementations of these functions would have to be updated.
+These would be stable APIs with an unstable implementation. If LLVM assembler syntax changes, the implementations of these functions would have to be updated.
 
 The embedded WG will submit an RFC proposing the `asm` module and that will include a list of assembly operations that (a) are common and (b) need to be inlined for different architectures.
 
 ### Unstable Feature #6: `#[used]`
 
-This experimental feature has been in the compiler for a while and it's required in some scenarios when using LTO to prevent the compiler some function / `static` that needs to be in the final binary.
+This experimental feature has been in the compiler for a while and it's required in some scenarios when using LTO to prevent the compiler from dead-stripping some function / `static` that needs to be in the final binary.
 
 We'll try to get it stabilized by the edition release but it's not a high priority feature.