Fix link on JS Guide

README.md

@@ -31,7 +31,7 @@ If you have any fixes or suggestions, simply send us a pull request!
 
 ### Running The Site Locally
 
-You will need [Ruby](https://www.ruby-lang.org/en/documentation/installation/), [Bundler](http://bundler.io/), and [npm](https://www.npmjs.com/get-npm).
+You will need [Ruby](https://www.ruby-lang.org/en/documentation/installation/), [Bundler](https://bundler.io/), and [npm](https://www.npmjs.com/get-npm).
 
 Clone this repository, then install Jekyll and node packages:
 

_config.yml

@@ -10,7 +10,7 @@ name: Parse Platform Docs
 title: Parse Docs
 email: community@parseplatform.org
 description: The open source docs for the Parse platform SDKs & other guides.
-url: "http://docs.parseplatform.org" # the base hostname & protocol for your site
+url: "https://docs.parseplatform.org" # the base hostname & protocol for your site
 repository: parse-community/docs
 twitter_username:  parseplatform
 github_username:   parseplatform

_includes/android/push-notifications.md

@@ -32,7 +32,7 @@ While it is possible to modify a `ParseInstallation` just like you would a `Pars
 *   **`appVersion`**: The version string of the client application to which this installation belongs. This value is synchronized every time a `ParseInstallation` object is saved from the device  _(readonly)_.
 *   **`parseVersion`**: The version of the Parse SDK which this installation uses. This value is synchronized every time a `ParseInstallation` object is saved from the device  _(readonly)_.
 *   **`timeZone`**: The current time zone where the target device is located. This value is synchronized every time a `ParseInstallation` object is saved from the device _(readonly)_.
-*   **`localeIdentifier`**: The locale identifier of the device in the format [language code]-[COUNTRY CODE]. The language codes are two-letter lowercase ISO language codes (such as "en") as defined by [ISO 639-1](http://en.wikipedia.org/wiki/ISO_639-1). The country codes are two-letter uppercase ISO country codes (such as "US") as defined by [ISO 3166-1](http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3). This value is synchronized every time a `ParseInstallation` object is saved from the device _(readonly)_.
+*   **`localeIdentifier`**: The locale identifier of the device in the format [language code]-[COUNTRY CODE]. The language codes are two-letter lowercase ISO language codes (such as "en") as defined by [ISO 639-1](https://en.wikipedia.org/wiki/ISO_639-1). The country codes are two-letter uppercase ISO country codes (such as "US") as defined by [ISO 3166-1](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3). This value is synchronized every time a `ParseInstallation` object is saved from the device _(readonly)_.
 *   **`badge`**: The current value of the icon badge for iOS apps. Changes to this value on the server will be used for future badge-increment push notifications.
 *   **`channelUris`**: The Microsoft-generated push URIs for Windows devices _(readonly)_.
 *   **`appIdentifier`**: A unique identifier for this installation's client application. This parameter is not supported in Android _(readonly)_.

_includes/android/queries.md

@@ -246,7 +246,7 @@ List<ParseObject> results = query.find();
 ```
 
 
-For Case or Diacritic Sensitive search, please use the [REST API](http://docs.parseplatform.org/rest/guide/#queries-on-string-values).
+For Case or Diacritic Sensitive search, please use the [REST API](https://docs.parseplatform.org/rest/guide/#queries-on-string-values).
 
 
 ## Relational Queries

_includes/android/roles.md

@@ -1,6 +1,6 @@
 # Roles
 
-As your app grows in scope and user-base, you may find yourself needing more coarse-grained control over access to pieces of your data than user-linked ACLs can provide. To address this requirement, Parse supports a form of [Role-based Access Control](http://en.wikipedia.org/wiki/Role-based_access_control). Roles provide a logical way of grouping users with common access privileges to your Parse data. Roles are named objects that contain users and other roles.  Any permission granted to a role is implicitly granted to its users as well as to the users of any roles that it contains.
+As your app grows in scope and user-base, you may find yourself needing more coarse-grained control over access to pieces of your data than user-linked ACLs can provide. To address this requirement, Parse supports a form of [Role-based Access Control](https://en.wikipedia.org/wiki/Role-based_access_control). Roles provide a logical way of grouping users with common access privileges to your Parse data. Roles are named objects that contain users and other roles.  Any permission granted to a role is implicitly granted to its users as well as to the users of any roles that it contains.
 
 For example, in your application with curated content, you may have a number of users that are considered "Moderators" and can modify and delete content created by other users.  You may also have a set of users that are "Administrators" and are allowed all of the same privileges as Moderators, but can also modify the global settings for the application. By adding users to these roles, you can ensure that new users can be made moderators or administrators, without having to manually grant permission to every resource for each user.
 

_includes/android/users.md

@@ -185,7 +185,7 @@ If you need to check if a `ParseUser` is authenticated, you can invoke the `isAu
 
 ## Security for Other Objects
 
-The same security model that applies to the `ParseUser` can be applied to other objects. For any object, you can specify which users are allowed to read the object, and which users are allowed to modify an object. To support this type of security, each object has an [access control list](http://en.wikipedia.org/wiki/Access_control_list), implemented by the `ParseACL` class.
+The same security model that applies to the `ParseUser` can be applied to other objects. For any object, you can specify which users are allowed to read the object, and which users are allowed to modify an object. To support this type of security, each object has an [access control list](https://en.wikipedia.org/wiki/Access_control_list), implemented by the `ParseACL` class.
 
 The simplest way to use a `ParseACL` is to specify that an object may only be read or written by a single user. To create such an object, there must first be a logged in `ParseUser`. Then, `new ParseACL(user)` generates a `ParseACL` that limits access to that user. An object's ACL is updated when the object is saved, like any other property. Thus, to create a private note that can only be accessed by the current user:
 

_includes/cloudcode/cloud-code-advanced.md

@@ -53,7 +53,7 @@ You can specify query parameters to append to the end of the url by setting `par
 
 ```javascript
 Parse.Cloud.httpRequest({
-  url: 'http://www.google.com/search',
+  url: 'https://www.google.com/search',
   params: {
     q : 'Sean Plott'
   }
@@ -68,7 +68,7 @@ or as a raw `String` like this:
 
 ```javascript
 Parse.Cloud.httpRequest({
-  url: 'http://www.google.com/search',
+  url: 'https://www.google.com/search',
   params: 'q=Sean Plott'
 }).then(function(httpResponse) {
   console.log(httpResponse.text);
@@ -83,7 +83,7 @@ You can send HTTP Headers by setting the `header` attribute of the options objec
 
 ```javascript
 Parse.Cloud.httpRequest({
-  url: 'http://www.example.com/',
+  url: 'https://www.example.com/',
   headers: {
     'Content-Type': 'application/json;charset=utf-8'
   }

_includes/cloudcode/cloud-code.md

@@ -291,7 +291,7 @@ You can pass some data alongside the call if you want to customize the job execu
 
 We don't support at the moment job scheduling and highly recommend to use a 3rd party system for scheduling your jobs.
 
-- On [AWS Elastic Beanstalk](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features-managing-env-tiers.html#worker-periodictasks)
+- On [AWS Elastic Beanstalk](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features-managing-env-tiers.html#worker-periodictasks)
 - On [Google App Engine](https://cloud.google.com/appengine/docs/flexible/nodejs/scheduling-jobs-with-cron-yaml)
 - On [Heroku](https://devcenter.heroku.com/articles/scheduler#scheduling-jobs)
 

_includes/common/data.md

@@ -59,7 +59,7 @@ Normally, when objects are saved to Parse, they are automatically assigned a uni
 * Use a unique 10 character alphanumeric string as the value of your `objectId` fields.
 * Use a UTC timestamp in the ISO 8601 format when setting a value for the `createdAt` field or the `updatedAt` field.
 
-In addition to the exposed fields, objects in the Parse User class can also have the `bcryptPassword` field set. The value of this field is a `String` that is the bcrypt hashed password + salt in the modular crypt format described in this [StackOverflow answer](http://stackoverflow.com/a/5882472/1351961). Most OpenSSL based bcrypt implementations should have built-in methods to produce these strings.
+In addition to the exposed fields, objects in the Parse User class can also have the `bcryptPassword` field set. The value of this field is a `String` that is the bcrypt hashed password + salt in the modular crypt format described in this [StackOverflow answer](https://stackoverflow.com/a/5882472/1351961). Most OpenSSL based bcrypt implementations should have built-in methods to produce these strings.
 
 A file containing a `User` object could look like:
 

_includes/common/security.md

@@ -490,6 +490,7 @@ There are some special classes in Parse that don't follow all of the same securi
 |Update|normal behavior [5]|ignores CLP, but not ACL [7]|
 |Delete|normal behavior [5]|master key only [7]|
 |Add Field|normal behavior|normal behavior|
+{: .docs_table}
 
 1. Logging in, or `/parse/login` in the REST API, does not respect the Get CLP on the user class. Login works just based on username and password, and cannot be disabled using CLPs.
 

_includes/dotnet/getting-started.md

@@ -8,6 +8,6 @@ If you're familiar with web frameworks like ASP.NET MVC we've taken many of the
   This guide is for the .NET-based version of our SDK. If you are doing Windows 8 development using HTML and JavaScript, please see our <a href="{{ site.baseurl }}/js/guide">JavaScript guide</a>.
 </div></div>
 
-If you haven't installed the SDK yet, please [head over to the QuickStart guide]({{ page.quickstart }}) to get our SDK up and running in Visual Studio or Xamarin Studio. Note that our SDK requires Visual Studio 2012 or Xamarin Studio and targets .NET 4.5 applications, Windows Store apps, Windows Phone 8 apps, and [Xamarin.iOS 6.3+](http://docs.xamarin.com/releases/ios/xamarin.ios_6/xamarin.ios_6.3) or [Xamarin.Android 4.7+](http://docs.xamarin.com/releases/android/xamarin.android_4/xamarin.android_4.7) apps. You can also check out our [API Reference]({{ site.apis.dotnet }}) for more detailed information about our SDK.
+If you haven't installed the SDK yet, please [head over to the QuickStart guide]({{ page.quickstart }}) to get our SDK up and running in Visual Studio or Xamarin Studio. Note that our SDK requires Visual Studio 2012 or Xamarin Studio and targets .NET 4.5 applications, Windows Store apps, Windows Phone 8 apps, and [Xamarin.iOS 6.3+](https://github.com/xamarin/release-notes-archive/blob/master/release-notes/ios/xamarin.ios_6/xamarin.ios_6.3/index.md) or [Xamarin.Android 4.7+](https://github.com/xamarin/release-notes-archive/blob/master/release-notes/android/xamarin.android_4/xamarin.android_4.7/index.md) apps. You can also check out our [API Reference]({{ site.apis.dotnet }}) for more detailed information about our SDK.
 
-Parse's .NET SDK makes heavy use of the [Task-based Asynchronous Pattern](http://msdn.microsoft.com/en-us/library/hh873175.aspx) so that your apps remain responsive. You can use the [async and await](http://msdn.microsoft.com/en-us/library/hh191443.aspx) keywords in C# and Visual Basic to easily use these long-running tasks.
+Parse's .NET SDK makes heavy use of the [Task-based Asynchronous Pattern](https://docs.microsoft.com/en-us/dotnet/standard/asynchronous-programming-patterns/task-based-asynchronous-pattern-tap) so that your apps remain responsive. You can use the [async and await](https://docs.microsoft.com/en-us/previous-versions/hh191443(v=vs.140)) keywords in C# and Visual Basic to easily use these long-running tasks.

_includes/dotnet/push-notifications.md

@@ -42,7 +42,7 @@ While it is possible to modify a `ParseInstallation` just like you would a `Pars
 *   **`channels`**:
     An `IEnumerable<string>` of the channels to which a device is currently subscribed. In .NET, this field is accessible through the `Channels` property.
 *   **`timeZone`**: The current time zone where the target device is located. This field is readonly and can be accessed via the `TimeZone` property. This value is synchronized every time an `Installation` object is saved from the device.
-*   **`localeIdentifier`**: The locale identifier of the device in the format [language code]-[COUNTRY CODE]. The language codes are two-letter lowercase ISO language codes (such as "en") as defined by [ISO 639-1](http://en.wikipedia.org/wiki/ISO_639-1). The country codes are two-letter uppercase ISO country codes (such as "US") as defined by [ISO 3166-1](http://en.wikipedia.org/wiki/ISO_3166-1_alpha-3). This value is synchronized every time a `ParseInstallation` object is saved from the device _(readonly)_.
+*   **`localeIdentifier`**: The locale identifier of the device in the format [language code]-[COUNTRY CODE]. The language codes are two-letter lowercase ISO language codes (such as "en") as defined by [ISO 639-1](https://en.wikipedia.org/wiki/ISO_639-1). The country codes are two-letter uppercase ISO country codes (such as "US") as defined by [ISO 3166-1](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-3). This value is synchronized every time a `ParseInstallation` object is saved from the device _(readonly)_.
 *   **`deviceType`**: The type of device, "ios", "android", "winrt", "winphone", or "dotnet". This field is readonly and can be accessed via the `DeviceType` property.
 *   **`pushType`**: This field is reserved for directing Parse to the push delivery network to be used. If the device is registered to receive pushes via FCM, this field will be marked "gcm". If this device is not using FCM, it will be blank _(readonly)_.
 *   **`installationId`**: Unique Id for the device used by Parse. This field is readonly and can be accessed via the `InstallationId` property.
@@ -390,7 +390,7 @@ On Windows 8, a toast notification can pass a small payload to the launch handle
 virtual void OnLaunched(LaunchActivatedEventArgs args) {
     // 'args' contains arguments that are passed to the app
     // during its launch activation from a Toast.
-    // More on Toasts: http://msdn.microsoft.com/en-us/library/windows/apps/hh779727.aspx
+    // More on Toasts: https://docs.microsoft.com/en-us/previous-versions/windows/apps/hh779727(v=win.10)
     ParseAnalytics.TrackAppOpenedAsync(args);
 }
 ```

_includes/dotnet/roles.md

@@ -1,6 +1,6 @@
 # Roles
 
-As your app grows in scope and user-base, you may find yourself needing more coarse-grained control over access to pieces of your data than user-linked ACLs can provide. To address this requirement, Parse supports a form of [Role-based Access Control](http://en.wikipedia.org/wiki/Role-based_access_control). Roles provide a logical way of grouping users with common access privileges to your Parse data. Roles are named objects that contain users and other roles.  Any permission granted to a role is implicitly granted to its users as well as to the users of any roles that it contains.
+As your app grows in scope and user-base, you may find yourself needing more coarse-grained control over access to pieces of your data than user-linked ACLs can provide. To address this requirement, Parse supports a form of [Role-based Access Control](https://en.wikipedia.org/wiki/Role-based_access_control). Roles provide a logical way of grouping users with common access privileges to your Parse data. Roles are named objects that contain users and other roles.  Any permission granted to a role is implicitly granted to its users as well as to the users of any roles that it contains.
 
 For example, in your application with curated content, you may have a number of users that are considered "Moderators" and can modify and delete content created by other users.  You may also have a set of users that are "Administrators" and are allowed all of the same privileges as Moderators, but can also modify the global settings for the application. By adding users to these roles, you can ensure that new users can be made moderators or administrators, without having to manually grant permission to every resource for each user.