Markdown file consistency

README.markdown

@@ -92,7 +92,7 @@ listed below. If you submit an issue, please include a link to either of:
 ## Load path and rubygems
 
 Not everybody uses rubygems as their package management system. If this
-sounds odd to you, read http://gist.github.com/54177.
+sounds odd to you, read https://gist.github.com/54177.
 
 In light of this fact, these repositories are "require 'rubygems'" free. The
 included Rakefiles use Bundler, which effectively manages all of this for
@@ -118,7 +118,7 @@ from the rspec-dev directory, or you'll see `LoadError`s.
 
 If you get a `SSL error` in Windows, you can follow the instructions on this [link](https://gist.github.com/luislavena/f064211759ee0f806c88) to fix it.  
 
-If you get this error `Gem::InstallError: The redcarpet native gem requires installed build tools`, download the development kit from [http://rubyinstaller.org/downloads](http://rubyinstaller.org/downloads). You can follow the installation instructions [here](https://github.com/oneclick/rubyinstaller/wiki/Development-Kit).
+If you get this error `Gem::InstallError: The redcarpet native gem requires installed build tools`, download the development kit from [https://rubyinstaller.org/downloads](https://rubyinstaller.org/downloads). You can follow the installation instructions [here](https://github.com/oneclick/rubyinstaller/wiki/Development-Kit).
 
 ## different problem?
 

Rakefile

@@ -325,7 +325,7 @@ namespace :common_plaintext_files do
           if file.extname == ".yml"
             all.concat([
               "# This file was generated on #{Time.now.iso8601} from the rspec-dev repo.\n",
-              "# DO NOT modify it by hand as your changes will get lost the next time it is generated.\n"
+              "# DO NOT modify it by hand as your changes will get lost the next time it is generated.\n\n"
             ])
           else
             all.concat([

code_of_conduct.md

@@ -49,7 +49,7 @@ incident.
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage],
 version 1.3.0, available at
-[http://contributor-covenant.org/version/1/3/0/][version]
+[https://contributor-covenant.org/version/1/3/0/][version]
 
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/3/0/
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/3/0/

common_plaintext_files/BUILD_DETAIL.md.erb

@@ -35,7 +35,7 @@ The spec suite performs a couple extra checks that are worth noting:
   available for use in any context, we want to minimize how many bits of the standard
   library we load and use. Otherwise, RSpec's use of part of the standard library could
   mask a problem where a gem author forgets to load a part of the standard library they
-  rely on. The spec suite contains a spec that defines a whitelist of allowed loaded
+  rely on. The spec suite contains a spec that defines a list of allowed loaded
   stdlibs.
 
 In addition, we use [SimpleCov](https://github.com/colszowka/simplecov)
@@ -63,8 +63,8 @@ $ bin/cucumber
 
 ## YARD documentation
 
-RSpec uses [YARD](http://yardoc.org/) for API documentation on the [rspec.info site](http://rspec.info/).
-Our commitment to [SemVer](htp://semver.org) requires that we explicitly
+RSpec uses [YARD](https://yardoc.org/) for API documentation on the [rspec.info site](https://rspec.info/).
+Our commitment to [SemVer](https://semver.org) requires that we explicitly
 declare our public API, and our build uses YARD to ensure that every
 class, module and method has either been labeled `@private` or has at
 least some level of documentation. For new APIs, this forces us to make

common_plaintext_files/CODE_OF_CONDUCT.md

@@ -41,14 +41,14 @@ when an individual is representing the project or its community.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported by contacting one of the project maintainers listed at
-http://rspec.info/about/. All complaints will be reviewed and investigated
+https://rspec.info/about/. All complaints will be reviewed and investigated
 and will result in a response that is deemed necessary and appropriate to the
 circumstances. Maintainers are obligated to maintain confidentiality with
 regard to the reporter of an incident.
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage],
 version 1.3.0, available at
-[http://contributor-covenant.org/version/1/3/0/][version]
+[https://contributor-covenant.org/version/1/3/0/][version]
 
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/3/0/
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/3/0/

common_plaintext_files/CONTRIBUTING.md.erb

@@ -8,8 +8,8 @@ If you'd like to help make RSpec better, here are some ways you can contribute:
   - by running RSpec HEAD to help us catch bugs before new releases
   - by [reporting bugs you encounter](https://github.com/rspec/<%= project_name %>/issues/new) with [report template](#report-template)
   - by [suggesting new features](https://github.com/rspec/<%= project_name %>/issues/new)
-  - by improving RSpec's [Relish](https://relishapp.com/rspec) or [API](http://rspec.info/documentation/) documentation
-  - by improving [RSpec's website](http://rspec.info/) ([source](https://github.com/rspec/rspec.github.io))
+  - by improving RSpec's [Relish](https://relishapp.com/rspec) or [API](https://rspec.info/documentation/) documentation
+  - by improving [RSpec's website](https://rspec.info/) ([source](https://github.com/rspec/rspec.github.io))
   - by taking part in [feature and issue discussions](https://github.com/rspec/<%= project_name %>/issues)
   - by adding a failing test for reproducible [reported bugs](https://github.com/rspec/<%= project_name %>/issues)
   - by reviewing [pull requests](https://github.com/rspec/<%= project_name %>/pulls) and suggesting improvements

common_plaintext_files/DEVELOPMENT.md.erb

@@ -1,7 +1,7 @@
 # Development Setup
 
 Generally speaking, you only need to clone the project and install
-the dependencies with [Bundler](http://bundler.io/). You can either
+the dependencies with [Bundler](https://bundler.io/). You can either
 get a full RSpec development environment using
 [rspec-dev](https://github.com/rspec/rspec-dev#README) or you can
 set this project up individually.
@@ -17,7 +17,7 @@ Clone the repo:
 $ git clone [email protected]:rspec/<%= project_name %>.git
 ```
 
-Install the dependencies using [Bundler](http://bundler.io/):
+Install the dependencies using [Bundler](https://bundler.io/):
 
 ```
 $ cd <%= project_name %>
@@ -26,7 +26,7 @@ $ bundle install
 
 To minimize boot time and to ensure we don't depend upon any extra dependencies
 loaded by Bundler, our CI builds avoid loading Bundler at runtime
-by using Bundler's [`--standalone option`](http://myronmars.to/n/dev-blog/2012/03/faster-test-boot-times-with-bundler-standalone).
+by using Bundler's [`--standalone option`](https://myronmars.to/n/dev-blog/2012/03/faster-test-boot-times-with-bundler-standalone).
 While not strictly necessary (many/most of our contributors do not do this!),
 if you want to exactly reproduce our CI builds you'll want to do the same:
 
@@ -109,7 +109,7 @@ Here's a short, non-exhaustive checklist of things we typically ask contributors
 
 # Adding Docs
 
-RSpec uses [YARD](http://yardoc.org/) for its API documentation. To
+RSpec uses [YARD](https://yardoc.org/) for its API documentation. To
 ensure the docs render well, we recommend running a YARD server and
 viewing your edits in a browser.
 

travis/script/functions.sh

@@ -3,7 +3,7 @@ source $SCRIPT_DIR/travis_functions.sh
 source $SCRIPT_DIR/predicate_functions.sh
 
 # If JRUBY_OPTS isn't set, use these.
-# see http://docs.travis-ci.com/user/ci-environment/
+# see https://docs.travis-ci.com/user/ci-environment/
 export JRUBY_OPTS=${JRUBY_OPTS:-"--server -Xcompile.invokedynamic=false"}
 SPECS_HAVE_RUN_FILE=specs.out
 MAINTENANCE_BRANCH=`cat maintenance-branch`