change http to https where applicable

CONTRIBUTING.md

@@ -1,5 +1,5 @@
-Welcome! Thanks for your interest in contributing to jquery.org. You're **almost** in the right place. More information on how to contribute to this and all other jQuery Foundation projects is over at [contribute.jquery.org](http://contribute.jquery.org). You'll definitely want to take a look at the articles on contributing [to our websites](http://contribute.jquery.org/web-sites/).
+Welcome! Thanks for your interest in contributing to jquery.org. You're **almost** in the right place. More information on how to contribute to this and all other jQuery Foundation projects is over at [contribute.jquery.org](https://contribute.jquery.org). You'll definitely want to take a look at the articles on contributing [to our websites](https://contribute.jquery.org/web-sites/).
 
-You may also want to take a look at our [commit & pull request guide](http://contribute.jquery.org/commits-and-pull-requests/) and [style guides](http://contribute.jquery.org/style-guide/) for instructions on how to maintain your fork and submit your code. Before we can merge any pull request, we'll also need you to sign our [contributor license agreement](http://contribute.jquery.org/cla).
+You may also want to take a look at our [commit & pull request guide](https://contribute.jquery.org/commits-and-pull-requests/) and [style guides](https://contribute.jquery.org/style-guide/) for instructions on how to maintain your fork and submit your code. Before we can merge any pull request, we'll also need you to sign our [contributor license agreement](https://contribute.jquery.org/cla).
 
-You can find us on [IRC](http://irc.jquery.org), specifically in #jquery-content should you have any questions. If you've never contributed to open source before, we've put together [a short guide with tips, tricks, and ideas on getting started](http://contribute.jquery.org/open-source/).
+You can find us on [IRC](https://irc.jquery.org), specifically in #jquery-content should you have any questions. If you've never contributed to open source before, we've put together [a short guide with tips, tricks, and ideas on getting started](https://contribute.jquery.org/open-source/).

README.md

@@ -2,7 +2,7 @@
 
 ## Building and Deploying
 
-To build and deploy your changes for previewing in a [`jquery-wp-content`](https://github.com/jquery/jquery-wp-content) instance, follow the [workflow instructions](http://contribute.jquery.org/web-sites/#workflow) from our documentation on [contributing to jQuery Foundation web sites](http://contribute.jquery.org/web-sites/).
+To build and deploy your changes for previewing in a [`jquery-wp-content`](https://github.com/jquery/jquery-wp-content) instance, follow the [workflow instructions](https://contribute.jquery.org/web-sites/#workflow) from our documentation on [contributing to jQuery Foundation web sites](https://contribute.jquery.org/web-sites/).
 
 ### Foundation Documents
 

data/members/bronze.json

@@ -1,54 +1,54 @@
 [
-	{
-		"name": "Fort Point Legal",
-		"url": "http://fortpoint.me/"
-	},
-	{
-		"name": "appendTo",
-		"url": "http://appendto.com/"
-	},
-	{
-		"name": "Bocoup",
-		"url": "http://bocoup.com/"
-	},
-	{
-		"name": "Environments for Humans",
-		"url": "http://environmentsforhumans.com/"
-	},
-	{
-		"name": "Code School",
-		"url": "http://www.codeschool.com/"
-	},
-	{
-		"name": "SitePen",
-		"url": "http://www.sitepen.com/"
-	},
-	{
-		"name": "AgileFAQs",
-		"url": "http://agilefaqs.com/"
-	},
-	{
-		"name": "Barewalls",
-		"url": "http://barewalls.com/"
-	},
-	{
-		"name": "Dealspotr",
-		"url": "http://dealspotr.com/"
-	},
-	{
-		"name": "ChameleonJohn.com",
-		"url": "http://chameleonjohn.com/"
-	},
-	{
-		"name": "NAVER",
-		"url": "http://naver.com/"
-	},
-	{
-		"name": "ppedv",
-		"url": "http://ppedv.com/"
-	},
-	{
-		"name": "SerenataFlowers.com",
-		"url": "http://serenataflowers.com/"
-	}
+    {
+        "name": "Fort Point Legal",
+        "url": "http://fortpoint.me/"
+    },
+    {
+        "name": "appendTo",
+        "url": "http://appendto.com/"
+    },
+    {
+        "name": "Bocoup",
+        "url": "https://bocoup.com/"
+    },
+    {
+        "name": "Environments for Humans",
+        "url": "http://environmentsforhumans.com/"
+    },
+    {
+        "name": "Code School",
+        "url": "https://www.codeschool.com/"
+    },
+    {
+        "name": "SitePen",
+        "url": "https://www.sitepen.com/"
+    },
+    {
+        "name": "AgileFAQs",
+        "url": "http://agilefaqs.com/"
+    },
+    {
+        "name": "Barewalls",
+        "url": "http://barewalls.com/"
+    },
+    {
+        "name": "Dealspotr",
+        "url": "https://dealspotr.com/"
+    },
+    {
+        "name": "ChameleonJohn.com",
+        "url": "http://chameleonjohn.com/"
+    },
+    {
+        "name": "NAVER",
+        "url": "http://naver.com/"
+    },
+    {
+        "name": "ppedv",
+        "url": "http://ppedv.com/"
+    },
+    {
+        "name": "SerenataFlowers.com",
+        "url": "https://serenataflowers.com/"
+    }
 ]

pages/conduct/changes.md

@@ -5,7 +5,7 @@
 
 ## Change control process
 
-We're (mostly) programmers, so we'll track changes to the code of conduct and associated documents the same way we track changes to code. All changes will be proposed via a pull request to the [jquery.org repository on GitHub](http://github.com/jquery/jquery.org). Changes will be reviewed by the conduct committee first, and then sent to the jQuery Foundation, the development teams, and the community for comment. We'll hold a comment period of at least one week, and then each group will vote on the change using its normal process (a board for the jQuery Foundation and project leads for the dev teams). Approved changes will be merged, published, and noted below.
+We're (mostly) programmers, so we'll track changes to the code of conduct and associated documents the same way we track changes to code. All changes will be proposed via a pull request to the [jquery.org repository on GitHub](https://github.com/jquery/jquery.org). Changes will be reviewed by the conduct committee first, and then sent to the jQuery Foundation, the development teams, and the community for comment. We'll hold a comment period of at least one week, and then each group will vote on the change using its normal process (a board for the jQuery Foundation and project leads for the dev teams). Approved changes will be merged, published, and noted below.
 
 This only applies to material changes; changes that don't effect the intent (typo fixes, re-wordings, etc.) can be made immediately.