Reformat README in Markdown

Author: diwakergupta

generator/README.asciidoc generator/README.mdgenerator/README.asciidoc renamed to generator/README.md

@@ -1,27 +1,27 @@
-= Dropbox Go SDK Generator
+# Dropbox Go SDK Generator
 
-This directory contains the https://github.com/dropbox/stone[Stone] code generators
-used to programmatically generate the https://github.com/dropbox/dropbox-sdk-go[Dropbox Go SDK].
+This directory contains the [Stone](https://github.com/dropbox/stone) code generators
+used to programmatically generate the [Dropbox Go SDK](https://github.com/dropbox/dropbox-sdk-go).
 
-== Requirements
+## Requirements
 
   * While not a hard requirement, this repo currently assumes `python3` in the path.
-  * Assumes you have already installed https://github.com/dropbox/stone[Stone]
-  * Requires https://godoc.org/golang.org/x/tools/cmd/goimports[goimports] to fix up imports in the auto-generated code
+  * Assumes you have already installed [Stone](https://github.com/dropbox/stone)
+  * Requires [goimports](https://godoc.org/golang.org/x/tools/cmd/goimports) to fix up imports in the auto-generated code
 
-== Basic Setup
+## Basic Setup
 
   . Clone this repo
   . Run `git submodule init` followed by `git submodule update`
   . Run `./generate-sdk.sh` to generate code under `../dropbox`
 
-== Generated Code
+## Generated Code
 
-=== Structs
+### Structs
 
 Stone https://github.com/dropbox/stone/blob/master/doc/lang_ref.rst#struct[structs] are represented as Go https://gobyexample.com/structs[structs] in a relatively straight-forward manner.
 
-----
+```
 struct Account <1>
     "The amount of detail revealed about an account depends on the user
     being queried and the user making the query." <2>
@@ -30,10 +30,9 @@ struct Account <1>
         "The user's unique Dropbox ID." <4>
     name Name <5>
         "Details of a user's name."
-----
+```
 
-[source,go]
-----
+```go
 // The amount of detail revealed about an account depends on the user being
 // queried and the user making the query. <2>
 type Account struct {  // <1>
@@ -42,29 +41,28 @@ type Account struct {  // <1>
   // Details of a user's name.
   Name *Name `json:"name"` // <5>
 }
-----
+```
 <1> A struct is defined as a Go struct
 <2> The documentation shows up before the struct definition
 <3> Each struct member is exported and also gets assigned the correct json tag. The latter is used for serializing requests and deserializing responses.
 <4> Member documentation appears above the member definition
 <5> Non-primitive types are represented as pointers to the corresponding type
 
-=== Unions
+### Unions
 
 Stone https://github.com/dropbox/stone/blob/master/doc/lang_ref.rst#union[unions] are bit more complex as Go doesn't have native support for union types (tagged or otherwise). We declare a union as a Go struct with all the possible fields as pointer types, and then use the tag value to populate the correct field during deserialization. This necessitates the use of an intermedia wrapper struct for the deserialization to work correctly, see below for a concrete example.
 
-----
+```
 union SpaceAllocation
     "Space is allocated differently based on the type of account."
 
     individual IndividualSpaceAllocation
         "The user's space allocation applies only to their individual account."
     team TeamSpaceAllocation
         "The user shares space with other members of their team."
-----
+```
 
-[source,go]
-----
+```go
 // Space is allocated differently based on the type of account.
 type SpaceAllocation struct { // <1>
   Tag string `json:".tag"` // <2>
@@ -103,7 +101,7 @@ func (u *SpaceAllocation) UnmarshalJSON(body []byte) error { // <4>
   }
   return nil
 }
-----
+```
 <1> A babel union is represented as Go struct
 <2> The tag value is used to determine which field is actually set
 <3> Possible values are represented as pointer types. Note the `omitempty` in the JSON tag; this is so values not set are automatically elided during serialization.
@@ -113,15 +111,15 @@ func (u *SpaceAllocation) UnmarshalJSON(body []byte) error { // <4>
 <7> When we deserialize response into the wrapper struct, it should get the tag value and the raw JSON as part of the members.
 <8> We then use the tag value to deserialize the `RawMessage` into the appropriate member of the union type
 
-=== Struct with Enumerated Subtypes
+### Struct with Enumerated Subtypes
 
 Per the https://github.com/dropbox/stone/blob/master/doc/lang_ref.rst#struct-polymorphism[spec], structs with enumerated subtypes are a mechanism of inheritance:
 
 > If a struct enumerates its subtypes, an instance of any subtype will satisfy the type constraint.
 
 So to represent structs with enumerated subtypes in Go, we use a strategy similar to unions. The _base_ struct (the one that defines the subtypes) is represented like we represent a union above. The _subtype_ is represented as a struct that essentially duplicates all fields of the base type and includes fields specific to that subtype. Here's an example:
 
-----
+```
 struct Metadata
     "Metadata for a file or folder."
 
@@ -138,13 +136,12 @@ struct Metadata
 struct FileMetadata extends Metadata
     id Id? #<2>
    ...
-----
+```
 <1> Field common to all subtypes
 <2> Field specific to `FileMetadata`
 
 
-[source,go]
-----
+```go
 // Metadata for a file or folder.
 type Metadata struct { // <1>
   Tag     string           `json:".tag"`
@@ -161,7 +158,7 @@ type FileMetadata struct {
   ...
   Id string `json:"id,omitempty"` // <3>
 }
-----
+```
 <1> Subtype is represented like we represent unions as described above
 <2> Common fields are duplicated in subtypes
 <3> Subtype specific fields are included as usual in structs