Fix markdown according to markdownlint. (#454)

Author: rolfbjarne

BUILDING.md

@@ -8,16 +8,15 @@ There are two options to installing Xcode:
 
 1. Use automatic provisioning. This is done by executing `make provision` in `maccore/tools/tom-swifty`, but it may take a while to download Xcode unless you're in the Boston office, in which case it might be better to download Xcode manually (next option).
 
-2. Download Xcode manually from https://download.developer.apple.com/Developer_Tools/Xcode_9.2/Xcode_9.2.xip
+2. Download Xcode manually from [https://download.developer.apple.com/Developer_Tools/Xcode_9.2/Xcode_9.2.xip](https://download.developer.apple.com/Developer_Tools/Xcode_9.2/Xcode_9.2.xip)
 
-	1. Extract and copy Xcode_9.2.xip to `/Applications/Xcode_9.2.app` (if you already have Xcode 9.2 in `/Applications/Xcode92.app`, you can just create a symlink: `ln -s /Applications/Xcode92.app /Applications/Xcode_9.2.app`)
-	2. `sudo xcode-select -s /Applications/Xcode_9.2.app/`
+    1. Extract and copy Xcode_9.2.xip to `/Applications/Xcode_9.2.app` (if you already have Xcode 9.2 in `/Applications/Xcode92.app`, you can just create a symlink: `ln -s /Applications/Xcode92.app /Applications/Xcode_9.2.app`)
+    2. `sudo xcode-select -s /Applications/Xcode_9.2.app/`
 
 ### Notes
 
 * there are other requirements (e.g. `cmake`, `ninja`) that I already have, most of them are likely needed to build `xamarin-macios`. It’s possible that I have some for others reasons too. Please update this document if you find any missing requirements.
 
-
 ## Building
 
 Create a directory to dedicate to Binding Tools for Swift, e.g.
@@ -38,7 +37,7 @@ Build everything. This will build the swift dependency (only if needed [1]) and
 toolchain is available in Azure, and if so, download and use that version.
 This behavior can be overriden by doing `export FORCE_SWIFT_BUILD=1`.
 
-### Notes
+### Notes About Building
 
 The above steps are doing a **full debug** build for swift. [build-script](https://github.com/xamarin/swift/blob/swift-4.0-branch-tomswifty/utils/build-script) can also produce different builds, e.g.
 
@@ -53,15 +52,15 @@ Running `build-script` takes a **very long** time, so building extraneous local
 1. `cd maccore/tools/tom-swifty/tests/tom-swifty-test/`
 2. `make`
 
-### Notes
+### Notes About Testing
 
 * The new (incompatible but much more powerful) NUnit 3 runner means using the usual `FIXTURES` variable has to use a [different syntax](https://github.com/nunit/docs/wiki/Test-Selection-Language). E.g. to run a single test case from the command line you would do
 
-```
+```shell
 FIXTURES="--where=test=SwiftReflector.LinkageTests.TestMissingNSObject" make
 ```
 
-
 ## Generated Source Files
-- `SwiftReflector/IOUtils/SwiftModuleList.g.cs` is generated via the `update_module_list.csharp` script. 
-	- `./update_module_list.csharp SwiftToolchain-v2-8efccc1464890d6c906fb2c40f909b5324da950d`
+
+* `SwiftReflector/IOUtils/SwiftModuleList.g.cs` is generated via the `update_module_list.csharp` script.
+    * `./update_module_list.csharp SwiftToolchain-v2-8efccc1464890d6c906fb2c40f909b5324da950d`

CONTRIBUTING.md

@@ -3,7 +3,7 @@
 This project welcomes contributions and suggestions. Most contributions require you to
 agree to a Contributor License Agreement (CLA) declaring that you have the right to,
 and actually do, grant us the rights to use your contribution. For details, visit
-https://cla.microsoft.com.
+[https://cla.microsoft.com](https://cla.microsoft.com).
 
 When you submit a pull request, a CLA-bot will automatically determine whether you need
 to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the

QUICKSTART.md

@@ -62,7 +62,7 @@ When you make binding-tools-for-swift, the build will bring down a copy of the b
     /path/to/binding-tools-for-swift/SwiftToolchain-v3/GITHASH/build/Ninja-ReleaseAssert/swift-macosx-x86_64/bin
     /path/to/binding-tools-for-swift/SwiftToolchain-v3/GITHASH/build/Ninja-ReleaseAssert/swift-macosx-x86_64/lib
 
-Since the binding tools need to compile Swift wrappers that use some runtime glue, it needs a reference 
+Since the binding tools need to compile Swift wrappers that use some runtime glue, it needs a reference
 
 A typical set of commands to generate bindings is:
 
@@ -82,11 +82,12 @@ The binding tools need the following to operate:
 In addition, the tools can operator on separate `.swiftmodule` and `.dylib` files. This can be handled by using a `-M` argument for the `.swiftmodule` and `-L` for the library. It’s easier to use the `.framework` directory and a single `-C` argument.
 
 ## Building and Running Samples
+
 Samples source code is in the `samples` directory, but will not build and run there.
 Instead you need to make a packaged build, from the root of binding-tools-for-swift execute the command:
 
-	`make package`
-	
+    make package
+
 this will leave a directory inside of the directory `Pack-Man` named `binding-tools-for-swift` which contains buildable samples.
 Most samples can be built by executing `make` in their directory. To try out a sample, do `make runit` for most of the samples.
 

README.md

@@ -19,6 +19,7 @@ In order to contribute to Binding-Tools-For-Swift, you will need Xcode 10.2 !
 ## Current Status
 
 ### What Binds?
+
 - Classes
 - Structs
 - Enums
@@ -32,11 +33,13 @@ In order to contribute to Binding-Tools-For-Swift, you will need Xcode 10.2 !
 - Extensions
 
 ### What Doesn’t Bind Yet?
+
 - Protocols with associated types
 - Bound generic types with closures
 - Non-escaping closures
 
 ### What Else Can I Expect?
+
 - An `open` class in Swift can be subclassed in C# and the subclass can be passed in to Swift. Overridden virtual methods in C# will be called when invoked from Swift.
 - A C# type implementing an interface bound to a Swift protocol can be passed in to Swift. Methods and properties in the C# interface implementation will be called when invoked from Swift.
 - At runtime, the generated code honors the Swift Automatic Reference Counting as well as .NET garbage collection.