Add examples for Creative Commons licenses and OFL

Also adjust instructions in README.md to match CONTRIBUTING.md

README.md

@@ -17,8 +17,8 @@ We catalog [select](CONTRIBUTING.md#adding-a-license) open source licenses with
 ```bash
 git clone https://github.com/github/choosealicense.com.git
 cd choosealicense.com
-script/bootstrap
-script/server
+./script/bootstrap
+./script/server
 ```
 
 Open `http://localhost:4000` in your favorite browser.

_licenses/cc-by-4.0.txt

@@ -7,6 +7,9 @@ description: Permits almost any use subject to providing credit and license noti
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. It is also acceptable to solely supply a link to a copy of the license, usually to the <a href='https://creativecommons.org/licenses/by/4.0/'>canonical URL for the license</a>.
 
 using:
+  - caniuse: https://github.com/Fyrd/caniuse/blob/master/LICENSE
+  - WHATWG HTML standard: https://github.com/whatwg/html/blob/master/LICENSE
+  - Kubernetes documentation: https://github.com/kubernetes/website/blob/master/LICENSE
 
 permissions:
   - commercial-use

_licenses/cc-by-sa-4.0.txt

@@ -7,6 +7,9 @@ description: Similar to <a href='/licenses/cc-by-4.0/'>CC-BY-4.0</a> but require
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. It is also acceptable to solely supply a link to a copy of the license, usually to the <a href='https://creativecommons.org/licenses/by-sa/4.0/'>canonical URL for the license</a>.
 
 using:
+  - Flight rules for Git: https://github.com/k88hudson/git-flight-rules/blob/master/LICENSE
+  - GitHub-Dark: https://github.com/StylishThemes/GitHub-Dark/blob/master/LICENSE
+  - Material Design Iconic Font: https://github.com/zavoloklom/material-design-iconic-font/blob/master/License.md
 
 permissions:
   - commercial-use

_licenses/cc0-1.0.txt

@@ -10,6 +10,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
 note: Creative Commons recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be <a href="https://wiki.creativecommons.org/wiki/CC0_FAQ#May_I_apply_CC0_to_computer_software.3F_If_so.2C_is_there_a_recommended_implementation.3F">found on their website</a>.
 
 using:
+  - Awesome: https://github.com/sindresorhus/awesome/blob/master/license
+  - Shields.io: https://github.com/badges/shields/blob/master/LICENSE
+  - psdash: https://github.com/Jahaja/psdash/blob/master/LICENSE
 
 permissions:
   - commercial-use

_licenses/ofl-1.1.txt

@@ -10,6 +10,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
 note: This license doesn't require source provision, but recommends it. All files derived from OFL files must remain licensed under the OFL.
 
 using:
+  - FiraCode: https://github.com/tonsky/FiraCode/blob/master/LICENSE
+  - Noto fonts: https://github.com/googlefonts/noto-fonts/blob/master/LICENSE
+  - Fantasque Sans Mono: https://github.com/belluzj/fantasque-sans/blob/master/LICENSE.txt
 
 permissions:
   - private-use

spec/license_meta_spec.rb

@@ -28,16 +28,12 @@ describe 'license meta' do
           'artistic-2.0',
           'bsd-3-clause-clear',
           'bsl-1.0',
-          'cc0-1.0',
-          'cc-by-4.0',
-          'cc-by-sa-4.0',
           'eupl-1.1',
           'lgpl-2.1',
           'lgpl-3.0',
           'lppl-1.3c',
           'ms-pl',
           'ms-rl',
-          'ofl-1.1',
           'wtfpl',
           'zlib'
         ]