docs: update GSoD blog post and remote add cmd ref

content/blog/2020-04-30-gsod-ideas-2020.md

@@ -159,7 +159,11 @@ technical writer, [Jorge](https://github.com/jorgeorpinel).
    [release history](https://github.com/iterative/dvc/releases) are not
    completely backward-compatible. We expect that fully updating all our
    previous docs will take a few months, and you could help us with this! The
-   main new features are:
+   main new features are listed below.
+
+   > UPDATE: See [post](https://dvc.org/blog/dvc-3-years-and-1-0-release) about
+   > the release! And corresponding docs
+   > [epic](https://github.com/iterative/dvc.org/issues/1255) task
 
    - A
      [multi-stage _pipelines file_](https://github.com/iterative/dvc/issues/1871)

content/docs/command-reference/remote/add.md

@@ -159,16 +159,17 @@ For more information about the variables DVC supports, please visit
 ### Click for Microsoft Azure Blob Storage
 
 ```dvc
-$ dvc remote add myremote azure://my-container-name/path
-$ dvc remote modify --local myremote connection_string "my-connection-string"
+$ dvc remote add --local myremote azure://my-container-name/path
+$ dvc remote modify --local myremote connection_string \
+                            "my-connection-string"
 ```
 
 > The connection string contains access to data and is inserted into the
-> `.dvc/config` file. Therefore, it is safer to add the connection string with
-> the `--local` option, enforcing it to be written to a Git-ignored config file.
-> See `dvc remote modify` for a full list of Azure storage parameters.
+> `.dvc/config` file. Therefore, it is safer to add the remote with the
+> `--local` option, enforcing it to be written to a Git-ignored config file. See
+> `dvc remote modify` for a full list of Azure storage parameters.
 
-The Azure Blob Storage remote can also be configured entirely via environment
+The Azure Blob Storage remote can also be configured globally via environment
 variables:
 
 ```dvc