tawasuyu/taffy

* Remove markdown-lint.yml

* Double-check all code, not just changed code

* Revert "Remove markdown-lint.yml"

This reverts commit 8262fef39ffbef233d4707f8b154c2355689d6de.

* Format readme according to markdown-lint rules

diff --git a/.github/linters/.markdown-lint.yml b/.github/linters/.markdown-lint.yml
index da6285182..03bf5690a 100644
--- a/.github/linters/.markdown-lint.yml
+++ b/.github/linters/.markdown-lint.yml
@@ -18,10 +18,11 @@
 ###############
 # Rules by id #
 ###############
-MD013:
-  line_length: 160
+# MD013:
+#  line_length: 120
 
 #################
 # Rules by tags #
 #################
 # blank_lines: false  # Error on blank lines
+line_length: false # Ignore excessively long lines
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index e226a60d3..ef7ae04c1 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -90,6 +90,6 @@ jobs:
       - name: Run Markdown Lint
         uses: docker://ghcr.io/github/super-linter:slim-v4
         env:
-          VALIDATE_ALL_CODEBASE: false
+          VALIDATE_ALL_CODEBASE: true
           VALIDATE_MARKDOWN: true
           DEFAULT_BRANCH: master
diff --git a/README.md b/README.md
index e2caf8d2b..4fce73614 100644
--- a/README.md
+++ b/README.md
@@ -1,12 +1,17 @@
 # Stretch2
+
 [![GitHub CI](https://github.com/DioxusLabs/stretch/actions/workflows/ci.yml/badge.svg)](https://github.com/DioxusLabs/stretch/actions/workflows/ci.yml)
 [![crates.io](https://img.shields.io/crates/v/stretch2.svg)](https://crates.io/crates/stretch2)
 
 > THIS IS A FORK OF THE ORIGINAL STRETCH. CURRENTLY MAINTAINED BY DIOXUS.
 
-Stretch2 is an implementation of Flexbox written in [Rust](https://www.rust-lang.org). The goal of stretch2 is to provide a solid foundation for layout across all platforms with a specific focus on mobile. Long term we want stretch2 to not only support flexbox but also many other layout algorithms such as grid layout. Stretch was made for and powers https://visly.app.
+Stretch2 is an implementation of Flexbox written in [Rust](https://www.rust-lang.org).
+The goal of stretch2 is to provide a solid foundation for layout across all platforms with a specific focus on mobile.
+Long term we want stretch2 to not only support flexbox but also many other layout algorithms such as grid layout.
+Stretch was made for and powers <https://visly.app>.
 
 ## Goals
+
 Before using or contributing to stretch2 it is good to be aware of the core goals of the project. These are goals we are working towards, not necessarily features we currently support.
 
 - High performance
@@ -24,9 +29,11 @@ Before using or contributing to stretch2 it is good to be aware of the core goal
 - JavaScript / TypeScript
 
 ## Usage
+
 Stretch2 is built in Rust but comes with bindings to multiple languages and platforms so you can use it in a way that feels natural to your project.
 
 ### Rust
+
 ```toml
 # Cargo.toml
 
@@ -64,6 +71,7 @@ fn main() -> Result<(), stretch2::Error> {
 ```
 
 ### Android
+
 ```groovy
 // Build.gradle
 
@@ -94,6 +102,7 @@ Log.d(TAG, "width: ${layout.width}, height: ${layout.height}")
 ```
 
 ### iOS
+
 ```ruby
 # Podfile
 
@@ -114,6 +123,7 @@ print("width: \(layout.width), height: \(layout.height)")
 ```
 
 ### JavaScript
+
 ```bash
 > npm install --save stretch-layout
 ```
@@ -132,6 +142,7 @@ console.log(layout.width, layout.height);
 ```
 
 ## Contributing
+
 Contributions are very welcome. Though we ask that you open an issue or pull request early in the process (before writing code) so we can discuss solutions and additions before you start spending time on implementing them. There are some specific areas where we would be extra happy to receive contributions in.
 
 - Binary size reduction
@@ -145,6 +156,7 @@ Contributions are very welcome. Though we ask that you open an issue or pull req
 - Documentation & Examples
 
 ### Installation
+
 If you don't have Rust installed you have to do that first as well as install some components that we make use of to format and lint the codebase. For more on Rust see their [website](https://www.rust-lang.org).
 
 ```bash
@@ -164,9 +176,12 @@ cargo test
 If you have made any changes to the API you should also update and run tests for all the platform bindings located in `/bindings/*`.
 
 ### Testing
-Stretch2 is tested by validating that layouts written in stretch2 perform the same as in Chrome. This is done by rendering an equivalent layout in HTML and then generating a Rust test case which asserts that the resulting layout is the same when run through stretch.
 
-You can run these tests without setting up a webdriver environment but if you are looking to add any test case you will need to install [chromedriver](http://chromedriver.chromium.org). If you are developing on macOS this is easy to do through brew.
+Stretch2 is tested by validating that layouts written in stretch2 perform the same as in Chrome.
+This is done by rendering an equivalent layout in HTML and then generating a Rust test case which asserts that the resulting layout is the same when run through stretch.
+
+You can run these tests without setting up a webdriver environment but if you are looking to add any test case you will need to install [chromedriver](http://chromedriver.chromium.org).
+If you are developing on macOS this is easy to do through brew.
 
 ```bash
 brew tap homebrew/cask
@@ -178,7 +193,13 @@ Once you have chromedriver installed and available in `PATH` you can re-generate
 To add a new test case add another HTML file to `/test_fixtures` following the current tests as a template for new tests.
 
 ### Benchmarking
-Benchmarks build on the same infrastructure as testing, and actually benchmarks are automatically generated from test fixtures just like tests. Run `cargo bench` to run benchmarks locally.
+
+Benchmarks build on the same infrastructure as testing, and actually benchmarks are automatically generated from test fixtures just like tests.
+Run `cargo bench` to run benchmarks locally.
 
 ## Relationship to Yoga
-[Yoga](https://www.yogalayout.com) is a cross-platform implementation of Flexbox written in C. Yoga is a fantastic project but has some fundamental issues which we hope to resolve. Compared to Yoga we aim to have a stronger adherence to web standards, a flexible architecture eventually supporting multiple layout algorithms, and future performance improvements including multi-threaded layout. In addition to this we aim to use a safer language with a more modern codebase.
+
+[Yoga](https://www.yogalayout.com) is a cross-platform implementation of Flexbox written in C.
+Yoga is a fantastic project but has some fundamental issues which we hope to resolve.
+Compared to Yoga we aim to have a stronger adherence to web standards, a flexible architecture eventually supporting multiple layout algorithms, and future performance improvements including multi-threaded layout.
+In addition to this we aim to use a safer language with a more modern codebase.
diff --git a/bindings/swift/Example/Pods/Nimble/README.md b/bindings/swift/Example/Pods/Nimble/README.md
index dde7fc413..61c58b7d4 100644
--- a/bindings/swift/Example/Pods/Nimble/README.md
+++ b/bindings/swift/Example/Pods/Nimble/README.md
@@ -20,15 +20,17 @@ expect(["Atlantic", "Pacific"]).toNot(contain("Mississippi"))
 expect(ocean.isClean).toEventually(beTruthy())
 ```
 
-# How to Use Nimble
+## How to Use Nimble
 
 <!-- START doctoc generated TOC please keep comment here to allow auto update -->
 <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
 **Table of Contents**  *generated with [DocToc](https://github.com/thlorenz/doctoc)*
 
-- [Some Background: Expressing Outcomes Using Assertions in XCTest](#some-background-expressing-outcomes-using-assertions-in-xctest)
-- [Nimble: Expectations Using `expect(...).to`](#nimble-expectations-using-expectto)
-  - [Custom Failure Messages](#custom-failure-messages)
+- [Nimble](#nimble)
+  - [How to Use Nimble](#how-to-use-nimble)
+  - [Some Background: Expressing Outcomes Using Assertions in XCTest](#some-background-expressing-outcomes-using-assertions-in-xctest)
+  - [Nimble: Expectations Using `expect(...).to`](#nimble-expectations-using-expectto)
+    - [Custom Failure Messages](#custom-failure-messages)
   - [Type Safety](#type-safety)
   - [Operator Overloads](#operator-overloads)
   - [Lazily Computed Values](#lazily-computed-values)
@@ -36,7 +38,7 @@ expect(ocean.isClean).toEventually(beTruthy())
   - [Asynchronous Expectations](#asynchronous-expectations)
   - [Objective-C Support](#objective-c-support)
   - [Disabling Objective-C Shorthand](#disabling-objective-c-shorthand)
-- [Built-in Matcher Functions](#built-in-matcher-functions)
+  - [Built-in Matcher Functions](#built-in-matcher-functions)
   - [Type Checking](#type-checking)
   - [Equivalence](#equivalence)
   - [Identity](#identity)
@@ -49,15 +51,17 @@ expect(ocean.isClean).toEventually(beTruthy())
   - [Collection Membership](#collection-membership)
   - [Strings](#strings)
   - [Collection Elements](#collection-elements)
+    - [Swift](#swift)
+    - [Objective-C](#objective-c)
   - [Collection Count](#collection-count)
   - [Notifications](#notifications)
   - [Matching a value to any of a group of matchers](#matching-a-value-to-any-of-a-group-of-matchers)
   - [Custom Validation](#custom-validation)
-- [Writing Your Own Matchers](#writing-your-own-matchers)
-  - [PredicateResult](#predicateresult)
-  - [Lazy Evaluation](#lazy-evaluation)
-  - [Type Checking via Swift Generics](#type-checking-via-swift-generics)
-  - [Customizing Failure Messages](#customizing-failure-messages)
+  - [Writing Your Own Matchers](#writing-your-own-matchers)
+    - [PredicateResult](#predicateresult)
+    - [Lazy Evaluation](#lazy-evaluation)
+    - [Type Checking via Swift Generics](#type-checking-via-swift-generics)
+    - [Customizing Failure Messages](#customizing-failure-messages)
     - [Basic Customization](#basic-customization)
     - [Full Customization](#full-customization)
   - [Supporting Objective-C](#supporting-objective-c)
@@ -67,14 +71,14 @@ expect(ocean.isClean).toEventually(beTruthy())
     - [Convert to use `Predicate` Type with Old Matcher Constructor](#convert-to-use-predicate-type-with-old-matcher-constructor)
     - [Convert to `Predicate` Type with Preferred Constructor](#convert-to-predicate-type-with-preferred-constructor)
     - [Deprecation Roadmap](#deprecation-roadmap)
-- [Installing Nimble](#installing-nimble)
-  - [Installing Nimble as a Submodule](#installing-nimble-as-a-submodule)
-  - [Installing Nimble via CocoaPods](#installing-nimble-via-cocoapods)
-  - [Using Nimble without XCTest](#using-nimble-without-xctest)
+  - [Installing Nimble](#installing-nimble)
+    - [Installing Nimble as a Submodule](#installing-nimble-as-a-submodule)
+    - [Installing Nimble via CocoaPods](#installing-nimble-via-cocoapods)
+    - [Using Nimble without XCTest](#using-nimble-without-xctest)
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
 
-# Some Background: Expressing Outcomes Using Assertions in XCTest
+## Some Background: Expressing Outcomes Using Assertions in XCTest
 
 Apple's Xcode includes the XCTest framework, which provides
 assertion macros to test whether code behaves properly.
@@ -104,7 +108,7 @@ XCTest assertions have a couple of drawbacks:
 
 Nimble addresses these concerns.
 
-# Nimble: Expectations Using `expect(...).to`
+## Nimble: Expectations Using `expect(...).to`
 
 Nimble allows you to express expectations using a natural,
 easily understood language:
@@ -150,7 +154,7 @@ expect(seagull.squawk).toNot(equal(@"Oh, hello there!"));
 expect(seagull.squawk).notTo(equal(@"Oh, hello there!"));
 ```
 
-## Custom Failure Messages
+### Custom Failure Messages
 
 Would you like to add more information to the test's failure messages? Use the `description` optional argument to add your own text:
 
@@ -315,7 +319,6 @@ DispatchQueue.main.async {
 expect(ocean).toEventually(contain("dolphins", "whales"))
 ```
 
-
 ```objc
 // Objective-C
 
@@ -465,9 +468,9 @@ to keep in mind when using Nimble in Objective-C:
 
 The following types are currently converted to an `NSObject` type:
 
- - **C Numeric types** are converted to `NSNumber *`
- - `NSRange` is converted to `NSValue *`
- - `char *` is converted to `NSString *`
+- **C Numeric types** are converted to `NSNumber *`
+- `NSRange` is converted to `NSValue *`
+- `char *` is converted to `NSString *`
 
 For the following matchers:
 
@@ -505,7 +508,7 @@ NMB_expect(^{ return seagull.squawk; }, __FILE__, __LINE__).to(NMB_equal(@"Squee
   `equal`. If that's not the case, there's no point in disabling the
   shorthand.
 
-# Built-in Matcher Functions
+## Built-in Matcher Functions
 
 Nimble includes a wide variety of matcher functions.
 
@@ -613,16 +616,15 @@ expect(actual) !== expected
 ```
 
 It is important to remember that `beIdenticalTo` only makes sense when comparing
-types with reference semantics, which have a notion of identity. In Swift, 
-that means types that are defined as a `class`. 
+types with reference semantics, which have a notion of identity. In Swift,
+that means types that are defined as a `class`.
 
 This matcher will not work when comparing types with value semantics such as
 those defined as a `struct` or `enum`. If you need to compare two value types,
 consider what it means for instances of your type to be identical. This may mean
-comparing individual properties or, if it makes sense to do so, conforming your type 
+comparing individual properties or, if it makes sense to do so, conforming your type
 to `Equatable` and using Nimble's equivalence matchers instead.
 
-
 ```objc
 // Objective-C
 
@@ -703,7 +705,8 @@ expect(actual) ≈ expected
 expect(actual) ≈ (expected, delta)
 
 ```
-(Type <kbd>option</kbd>+<kbd>x</kbd> to get `≈` on a U.S. keyboard)
+
+(Type `Option + X` to get `≈` on a U.S. keyboard)
 
 The former version uses the default delta of 0.0001. Here is yet another way to do this:
 
@@ -714,7 +717,8 @@ expect(actual) ≈ expected ± delta
 expect(actual) == expected ± delta
 
 ```
-(Type <kbd>option</kbd>+<kbd>shift</kbd>+<kbd>=</kbd> to get `±` on a U.S. keyboard)
+
+(Type `Option + "+"` to get `±` on a U.S. keyboard)
 
 If you are comparing arrays of floating point numbers, you'll find the following useful:
 
@@ -840,9 +844,9 @@ expect(reachedPoint2) == false
 
 Notes:
 
-* This feature is only available in Swift.
-* It is only supported for `x86_64` binaries, meaning _you cannot run this matcher on iOS devices, only simulators_.
-* The tvOS simulator is supported, but using a different mechanism, requiring you to turn off the `Debug executable` scheme setting for your tvOS scheme's Test configuration.
+- This feature is only available in Swift.
+- It is only supported for `x86_64` binaries, meaning *you cannot run this matcher on iOS devices, only simulators*.
+- The tvOS simulator is supported, but using a different mechanism, requiring you to turn off the `Debug executable` scheme setting for your tvOS scheme's Test configuration.
 
 ## Swift Error Handling
 
@@ -872,7 +876,7 @@ explicitly cast the error.
 
 The `matchError` matcher allows you to check whether or not the error:
 
-- is the same _type_ of error you are expecting.
+- is the same *type* of error you are expecting.
 - represents a particular error value that you are expecting.
 
 This can be useful when using `Result` or `Promise` types, for example.
@@ -934,7 +938,7 @@ expect(actual).to(raiseException().satisfyingBlock(^(NSException *exception) {
 }));
 ```
 
-Note: Swift currently doesn't have exceptions (see [#220](https://github.com/Quick/Nimble/issues/220#issuecomment-172667064)). 
+Note: Swift currently doesn't have exceptions (see [#220](https://github.com/Quick/Nimble/issues/220#issuecomment-172667064)).
 Only Objective-C code can raise exceptions that Nimble will catch.
 
 ## Collection Membership
@@ -1162,10 +1166,10 @@ For example, instances of `Array`, `Dictionary`, or `Set`.
 
 For Objective-C, the actual value must be one of the following classes, or their subclasses:
 
- - `NSArray`,
- - `NSDictionary`,
- - `NSSet`, or
- - `NSHashTable`.
+- `NSArray`,
+- `NSDictionary`,
+- `NSSet`, or
+- `NSHashTable`.
 
 ## Notifications
 
@@ -1249,7 +1253,7 @@ The `String` provided with `.failed()` is shown when the test fails.
 
 When using `toEventually()` be careful not to make state changes or run process intensive code since this closure will be ran many times.
 
-# Writing Your Own Matchers
+## Writing Your Own Matchers
 
 In Nimble, matchers are Swift functions that take an expected
 value and return a `Predicate` closure. Take `equal`, for example:
@@ -1299,7 +1303,7 @@ For examples of how to write your own matchers, just check out the
 to see how Nimble's built-in set of matchers are implemented. You can
 also check out the tips below.
 
-## PredicateResult
+### PredicateResult
 
 `PredicateResult` is the return struct that `Predicate` return to indicate
 success and failure. A `PredicateResult` is made up of two values:
@@ -1356,7 +1360,7 @@ error with more details.
 A common message to append is failing on nils. For that, `.appendedBeNilHint()`
 can be used.
 
-## Lazy Evaluation
+### Lazy Evaluation
 
 `actualExpression` is a lazy, memoized closure around the value provided to the
 `expect` function. The expression can either be a closure or a value directly
@@ -1384,7 +1388,7 @@ that returns a value. The value it returns, which is accessed via the
 `evaluate()` method, may be `nil`. If that value is `nil`, the `beNil`
 matcher function returns `true`, indicating that the expectation passed.
 
-## Type Checking via Swift Generics
+### Type Checking via Swift Generics
 
 Using Swift's generics, matchers can constrain the type of the actual value
 passed to the `expect` function by modifying the return type.
@@ -1403,7 +1407,7 @@ public func haveDescription(description: String) -> Predicate<Printable?> {
 }
 ```
 
-## Customizing Failure Messages
+### Customizing Failure Messages
 
 When using `Predicate.simple(..)` or `Predicate.simpleNilable(..)`, Nimble
 outputs the following failure message when an expectation fails:
@@ -1664,8 +1668,7 @@ The deprecating plan is a 3 major versions removal. Which is as follows:
     `v9.x.x`)
  3. Remove old API. (Nimble `v10.x.x`)
 
-
-# Installing Nimble
+## Installing Nimble
 
 > Nimble can be used on its own, or in conjunction with its sister
   project, [Quick](https://github.com/Quick/Quick). To install both
@@ -1675,7 +1678,7 @@ The deprecating plan is a 3 major versions removal. Which is as follows:
 Nimble can currently be installed in one of two ways: using CocoaPods, or with
 git submodules.
 
-## Installing Nimble as a Submodule
+### Installing Nimble as a Submodule
 
 To use Nimble as a submodule to test your macOS, iOS or tvOS applications, follow
 these 4 easy steps:
@@ -1690,7 +1693,7 @@ read [How to Install Quick](https://github.com/Quick/Quick#how-to-install-quick)
 Ignore the steps involving adding Quick to your project in order to
 install just Nimble.
 
-## Installing Nimble via CocoaPods
+### Installing Nimble via CocoaPods
 
 To use Nimble in CocoaPods to test your macOS, iOS or tvOS applications, add
 Nimble to your podfile and add the ```use_frameworks!``` line to enable Swift
@@ -1711,14 +1714,14 @@ end
 
 Finally run `pod install`.
 
-## Using Nimble without XCTest
+### Using Nimble without XCTest
 
 Nimble is integrated with XCTest to allow it work well when used in Xcode test
 bundles, however it can also be used in a standalone app. After installing
 Nimble using one of the above methods, there are two additional steps required
 to make this work.
 
-1. Create a custom assertion handler and assign an instance of it to the
+First, create a custom assertion handler and assign an instance of it to the
    global `NimbleAssertionHandler` variable. For example:
 
 ```swift
@@ -1730,18 +1733,20 @@ class MyAssertionHandler : AssertionHandler {
     }
 }
 ```
+
 ```swift
 // Somewhere before you use any assertions
 NimbleAssertionHandler = MyAssertionHandler()
 ```
 
-2. Add a post-build action to fix an issue with the Swift XCTest support
-   library being unnecessarily copied into your app
-  * Edit your scheme in Xcode, and navigate to Build -> Post-actions
-  * Click the "+" icon and select "New Run Script Action"
-  * Open the "Provide build settings from" dropdown and select your target
-  * Enter the following script contents:
-```
+Then, add a post-build action to fix an issue with the Swift XCTest support library being unnecessarily copied into your app
+
+- Edit your scheme in Xcode, and navigate to Build -> Post-actions
+- Click the "+" icon and select "New Run Script Action"
+- Open the "Provide build settings from" dropdown and select your target
+- Enter the following script contents:
+
+```sh
 rm "${SWIFT_STDLIB_TOOL_DESTINATION_DIR}/libswiftXCTest.dylib"
 ```
 
diff --git a/bindings/swift/Example/Pods/Quick/README.md b/bindings/swift/Example/Pods/Quick/README.md
index 2cb397f1d..510430593 100644
--- a/bindings/swift/Example/Pods/Quick/README.md
+++ b/bindings/swift/Example/Pods/Quick/README.md
@@ -1,4 +1,6 @@
-![](http://f.cl.ly/items/0r1E192C1R0b2g2Q3h2w/QuickLogo_Color.png)
+# Quick for Swift
+
+![The Quick library logo](http://f.cl.ly/items/0r1E192C1R0b2g2Q3h2w/QuickLogo_Color.png)
 
 [![Build Status](https://travis-ci.org/Quick/Quick.svg?branch=master)](https://travis-ci.org/Quick/Quick)
 [![CocoaPods](https://img.shields.io/cocoapods/v/Quick.svg)](https://cocoapods.org/pods/Quick)
@@ -9,7 +11,7 @@
 Quick is a behavior-driven development framework for Swift and Objective-C.
 Inspired by [RSpec](https://github.com/rspec/rspec), [Specta](https://github.com/specta/specta), and [Ginkgo](https://github.com/onsi/ginkgo).
 
-![](https://raw.githubusercontent.com/Quick/Assets/master/Screenshots/QuickSpec%20screenshot.png)
+![A screenshot of the QuickSpec code in Swift.](https://raw.githubusercontent.com/Quick/Assets/master/Screenshots/QuickSpec%20screenshot.png)
 
 ```swift
 // Swift
@@ -36,12 +38,17 @@ class TableOfContentsSpec: QuickSpec {
   }
 }
 ```
-#### Nimble
-Quick comes together with [Nimble](https://github.com/Quick/Nimble) — a matcher framework for your tests. You can learn why `XCTAssert()` statements make your expectations unclear and how to fix that using Nimble assertions [here](./Documentation/en-us/NimbleAssertions.md).
+
+## Nimble
+
+Quick comes together with [Nimble](https://github.com/Quick/Nimble) — a matcher framework for your tests.
+You can learn why `XCTAssert()` statements make your expectations unclear and how to fix that using Nimble assertions [here](./Documentation/en-us/NimbleAssertions.md).
 
 ## Swift Version
 
-Certain versions of Quick and Nimble only support certain versions of Swift. Depending on which version of Swift your project uses, you should use specific versions of Quick and Nimble. Use the table below to determine which versions of Quick and Nimble are compatible with your project.
+Certain versions of Quick and Nimble only support certain versions of Swift.
+Depending on which version of Swift your project uses, you should use specific versions of Quick and Nimble.
+Use the table below to determine which versions of Quick and Nimble are compatible with your project.
 
 |Swift version        |Quick version   |Nimble version |
 |:--------------------|:---------------|:--------------|
@@ -51,7 +58,8 @@ Certain versions of Quick and Nimble only support certain versions of Swift. Dep
 
 ## Documentation
 
-All documentation can be found in the [Documentation folder](./Documentation), including [detailed installation instructions](./Documentation/en-us/InstallingQuick.md) for CocoaPods, Carthage, Git submodules, and more. For example, you can install Quick and [Nimble](https://github.com/Quick/Nimble) using CocoaPods by adding the following to your Podfile:
+All documentation can be found in the [Documentation folder](./Documentation), including [detailed installation instructions](./Documentation/en-us/InstallingQuick.md) for CocoaPods, Carthage, Git submodules, and more.
+For example, you can install Quick and [Nimble](https://github.com/Quick/Nimble) using CocoaPods by adding the following to your Podfile:
 
 ```rb
 # Podfile
@@ -74,17 +82,18 @@ end
 
 ## Projects using Quick
 
-Over ten-thousand apps use either Quick and Nimble however, as they are not included in the app binary, neither appear in “Top Used Libraries” blog posts. Therefore, it would be greatly appreciated to remind contributors that their efforts are valued by compiling a list of organizations and projects that use them. 
+Over ten-thousand apps use either Quick and Nimble however, as they are not included in the app binary, neither appear in “Top Used Libraries” blog posts.
+Therefore, it would be greatly appreciated to remind contributors that their efforts are valued by compiling a list of organizations and projects that use them.
 
 Does your organization or project use Quick and Nimble? If yes, [please add your project to the list](https://github.com/Quick/Quick/wiki/Projects-using-Quick).
 
 ## Who uses Quick
 
-Similar to projects using Quick, it would be nice to hear why people use Quick and Nimble. Are there features you love? Are there features that are just okay? Are there some features we have that no one uses?
+Similar to projects using Quick, it would be nice to hear why people use Quick and Nimble.
+Are there features you love? Are there features that are just okay? Are there some features we have that no one uses?
 
 Have something positive to say about Quick (or Nimble)? If yes, [provide a testimonial here](https://github.com/Quick/Quick/wiki/Who-uses-Quick).
 
-
 ## License
 
 Apache 2.0 license. See the [`LICENSE`](LICENSE) file for details.
diff --git a/bindings/swift/Example/Pods/Target Support Files/Pods-StretchKit_Tests/Pods-StretchKit_Tests-acknowledgements.markdown b/bindings/swift/Example/Pods/Target Support Files/Pods-StretchKit_Tests/Pods-StretchKit_Tests-acknowledgements.markdown
index 29f63dd8a..b6b0f85ac 100644
--- a/bindings/swift/Example/Pods/Target Support Files/Pods-StretchKit_Tests/Pods-StretchKit_Tests-acknowledgements.markdown	
+++ b/bindings/swift/Example/Pods/Target Support Files/Pods-StretchKit_Tests/Pods-StretchKit_Tests-acknowledgements.markdown	
@@ -1,11 +1,12 @@
 # Acknowledgements
+
 This application makes use of the following third party libraries:
 
 ## Nimble
 
 Apache License
                            Version 2.0, January 2004
-                        http://www.apache.org/licenses/
+                        <http://www.apache.org/licenses/>
 
    TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
 
@@ -205,12 +206,11 @@ Apache License
    See the License for the specific language governing permissions and
    limitations under the License.
 
-
 ## Quick
 
 Apache License
                            Version 2.0, January 2004
-                        http://www.apache.org/licenses/
+                        <http://www.apache.org/licenses/>
 
    TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
 
@@ -410,7 +410,6 @@ Apache License
    See the License for the specific language governing permissions and
    limitations under the License.
 
-
 ## StretchKit
 
 MIT License
@@ -435,5 +434,4 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
-
-Generated by CocoaPods - https://cocoapods.org
+Generated by CocoaPods - <https://cocoapods.org>