update docs

Author: bobzhang

_blogposts/2020-09-23-release-8-3.md.raw

@@ -25,7 +25,7 @@ The changes are listed [here](https://github.com/rescript-lang/rescript-compiler
 
 ## Lightweight FFI attributes without `bs.` prefix
 
-In this release, we make it optional to have `bs.` prefix it or not, this will make the FFI less verbose,
+In this release, we make the `bs.` prefix optional, this will make the FFI less verbose.
 
 For example, the old externals for `readFileAsUtf8Sync` used to be written like this
 
@@ -34,18 +34,18 @@ For example, the old externals for `readFileAsUtf8Sync` used to be written like
 external readFileAsUtf8Sync : string -> (_[@bs.as "utf8"]) -> string = "readFileSync" [@@bs.val] [@@bs.module "fs"]
 ```
 
-Could be simplified as 
+It can now be simplified as 
 ```ocaml
 external readFileAsUtf8Sync : string -> (_[@as "utf8"]) -> string = "readFileSync" 
 [@@val] [@@module "fs"]
 ```
 
-Note almost all previous attributes with `bs.xx` can be simplified as `xx`, except such two that 
-we don't provide abbreviations:
+Note almost all previous attributes with `bs.xx` can be simplified as `xx` 
+with the exception of the following two that don't have abbreviations:
 
-- `bs.send.pipe` : this attribute was deprecated in favor of `bs.send`, you can still use the existing one for backward compatibility.
+- `bs.send.pipe` : this attribute was deprecated in favor of `bs.send`; you can still use the existing one for backward compatibility.
 
-- `bs.splice` : this attribute was deprecated in favor of `bs.variadic`, you can still use the existing one for 
+- `bs.splice` : this attribute was deprecated in favor of `bs.variadic`; you can still use the existing one for 
 backward compatibility.
 
 
@@ -84,13 +84,15 @@ Now user can pick up their js file extension support per module format:
 
 ## More flexible filename support
 
-To have better integration with other [JS infrastructures](https://github.com/rescript-lang/rescript-compiler/issues/4624), for example, Next.js/React Native, we allow file names like `404.res`, `Button.Andriod.res` so that it can just be picked up by those tools
+To have better integration with other [JS infrastructures](https://github.com/rescript-lang/rescript-compiler/issues/4624), 
+for example, Next.js/React Native, we allow file names like `404.res`, 
+`Button.Android.res` so that it can just be picked up by those tools
 
 
 
 ## Better type based inference for pattern `let {a,b,c} = value`
 
-Previously for such piece of code:
+Previously, for code like this:
 
 ```ocaml
 module N = struct 
@@ -109,8 +111,9 @@ You will get a type error
 Error: Unbound record field x
 ```
 
-However, since the compiler already knows the type of `u`, it is capable of looking up the label `x` properly, 
-in this release, we make such style work out of the box without the work around like adding a module prefix like `let {N.x} = ..`
+However, since the compiler already knows the type of `u`, it is capable of looking up the label `x` properly. 
+In this release, we make the original code style work out of the box without a work-around such as adding a module prefix 
+like `let {N.x} = ..`
 
 ## Build system enhancement 
 

_blogposts/2020-09-23-release-8-3.mdx

@@ -25,7 +25,7 @@ The changes are listed [here](https://github.com/rescript-lang/rescript-compiler
 
 ## Lightweight FFI attributes without `bs.` prefix
 
-In this release, we make it optional to have `bs.` prefix it or not, this will make the FFI less verbose,
+In this release, we make the `bs.` prefix optional, this will make the FFI less verbose.
 
 For example, the old externals for `readFileAsUtf8Sync` used to be written like this
 
@@ -45,7 +45,7 @@ external readFileAsUtf8Sync : string -> (_[@bs.as "utf8"]) -> string = "readFile
 ```
 </CodeTab>
 
-Could be simplified as 
+It can now be simplified as 
 <CodeTab labels={["ReScript", "Reason", "ML"]}>
 ```res
 @val @module("fs") external readFileAsUtf8Sync: (string, @as("utf8") _) => string = "readFileSync"
@@ -61,12 +61,12 @@ external readFileAsUtf8Sync : string -> (_[@as "utf8"]) -> string = "readFileSyn
 ```
 </CodeTab>
 
-Note almost all previous attributes with `bs.xx` can be simplified as `xx`, except such two that 
-we don't provide abbreviations:
+Note almost all previous attributes with `bs.xx` can be simplified as `xx` 
+with the exception of the following two that don't have abbreviations:
 
-- `bs.send.pipe` : this attribute was deprecated in favor of `bs.send`, you can still use the existing one for backward compatibility.
+- `bs.send.pipe` : this attribute was deprecated in favor of `bs.send`; you can still use the existing one for backward compatibility.
 
-- `bs.splice` : this attribute was deprecated in favor of `bs.variadic`, you can still use the existing one for 
+- `bs.splice` : this attribute was deprecated in favor of `bs.variadic`; you can still use the existing one for 
 backward compatibility.
 
 
@@ -117,13 +117,15 @@ Now user can pick up their js file extension support per module format:
 
 ## More flexible filename support
 
-To have better integration with other [JS infrastructures](https://github.com/rescript-lang/rescript-compiler/issues/4624), for example, Next.js/React Native, we allow file names like `404.res`, `Button.Andriod.res` so that it can just be picked up by those tools
+To have better integration with other [JS infrastructures](https://github.com/rescript-lang/rescript-compiler/issues/4624), 
+for example, Next.js/React Native, we allow file names like `404.res`, 
+`Button.Android.res` so that it can just be picked up by those tools
 
 
 
 ## Better type based inference for pattern `let {a,b,c} = value`
 
-Previously for such piece of code:
+Previously, for code like this:
 
 <CodeTab labels={["ReScript", "Reason", "ML"]}>
 ```res
@@ -164,8 +166,9 @@ You will get a type error
 Error: Unbound record field x
 ```
 
-However, since the compiler already knows the type of `u`, it is capable of looking up the label `x` properly, 
-in this release, we make such style work out of the box without the work around like adding a module prefix like `let {N.x} = ..`
+However, since the compiler already knows the type of `u`, it is capable of looking up the label `x` properly. 
+In this release, we make the original code style work out of the box without a work-around such as adding a module prefix 
+like `let {N.x} = ..`
 
 ## Build system enhancement