Changed protocol to https where appropriate

Author: GeniusTimo

docs/activities/development-guides.mdx

@@ -442,7 +442,7 @@ User Experience
 
 An [Entry Point command](/docs/interactions/application-commands#entry-point-commands) is required for users to be able to launch your Activity from the [App Launcher menu](https://support.discord.com/hc/articles/21334461140375-Using-Apps-on-Discord#h_01HRQSA6C8TRHS722P1H3HW1TV) in Discord.
 
-When you enable Activities in your [app's settings](http://discord.com/developers/applications), a [default Entry Point command](/docs/interactions/application-commands#default-entry-point-command) is automatically created for your app. The default Entry Point command will use the `DISCORD_LAUNCH_ACTIVITY` (`2`) [handler type](/docs/interactions/application-commands#application-command-object-entry-point-command-handler-types), which means that Discord automatically launches your Activity for the user and posts a follow-up message into the channel where it was launched from.
+When you enable Activities in your [app's settings](https://discord.com/developers/applications), a [default Entry Point command](/docs/interactions/application-commands#default-entry-point-command) is automatically created for your app. The default Entry Point command will use the `DISCORD_LAUNCH_ACTIVITY` (`2`) [handler type](/docs/interactions/application-commands#application-command-object-entry-point-command-handler-types), which means that Discord automatically launches your Activity for the user and posts a follow-up message into the channel where it was launched from.
 
 If you want to handle sending messages yourself, you can update the handler to be `APP_HANDLER` (`1`). Details about Entry Point command handlers is in the [Entry Point command documentation](/docs/interactions/application-commands#entry-point-handlers).
 

docs/change-log/2024-03-18-discord-activities-developer-preview-of-the-embedded-app-sdk.md

@@ -11,7 +11,7 @@ Discord Developers can now build Activities!
 Activities are interactive, multiplayer experiences that run in an iframe in Discord. In order to make the communication between your experience and Discord, we've introduced the Embedded App SDK to assist in communicating between your app and the Discord client.
 
 * New [Discord Activities](/docs/activities/overview) developer docs with a tutorial, code samples, development guides, and design principles.
-* The Embedded App SDK is now available via [npm](https://npmjs.com/package/@discord/embedded-app-sdk) and [GitHub](http://github.com/discord/embedded-app-sdk).
+* The Embedded App SDK is now available via [npm](https://npmjs.com/package/@discord/embedded-app-sdk) and [GitHub](https://github.com/discord/embedded-app-sdk).
 * The [Embedded App SDK Reference](/docs/developer-tools/embedded-app-sdk) is now available.
 
 To learn more about how to get started building your own Activity, check out the [Activities Overview](/docs/activities/overview).

docs/change-log/2024-08-26-entry-point-commands.md

@@ -16,4 +16,4 @@ More details about Entry Point commands can be found in the [Application Command
 
 ### Default Entry Point Commands
 
-Starting today, when you enable Activities in your [app's settings](http://discord.com/developers/applications), a [default Entry Point command](/docs/interactions/application-commands#default-entry-point-command) called "Launch" will automatically be created for your app. This can be customized or deleted like other commands if you want to update the name or handler type.
+Starting today, when you enable Activities in your [app's settings](https://discord.com/developers/applications), a [default Entry Point command](/docs/interactions/application-commands#default-entry-point-command) called "Launch" will automatically be created for your app. This can be customized or deleted like other commands if you want to update the name or handler type.

docs/change-log/2025-03-17-introducing-the-discord-social-sdk.md

@@ -29,7 +29,7 @@ New resources are available in the Developer Portal to help you get started with
 - [Getting Started Guides](/docs/discord-social-sdk/getting-started) for C++, Unity and Unreal Engine.
 - [Development Guides](/docs/discord-social-sdk/development-guides) for building your game's social features.
 - [Design Guidelines](/docs/discord-social-sdk/design-guidelines) for designing your game's social features.
-- [SDK Reference](http://discord.com/developers/docs/social-sdk/index.html) is now available.
+- [SDK Reference](https://discord.com/developers/docs/social-sdk/index.html) is now available.
 - The Discord Social SDK binaries are available for download in the Developer Portal after enabling the Discord Social SDK for your application.
 
 To learn more about building with the Discord Social SDK, check out the [Discord Social SDK Overview](/docs/discord-social-sdk/overview).

docs/quick-start/getting-started.mdx

@@ -279,7 +279,7 @@ Click **Save Changes** and ensure your endpoint is successfully verified.
 > If you have troubles verifying your endpoint, make sure both ngrok and your app are running on the same port, and that you've copied the ngrok URL correctly
 
 The verification is handled automatically by the sample app in two ways:
-- It uses the `PUBLIC_KEY` and [discord-interactions package](https://github.com/discord/discord-interactions-js#usage) with a wrapper function (imported from `utils.js`) that makes it conform to [Express's `verify` interface](http://expressjs.com/en/5x/api.html#express.json). This is run on every incoming request to your app.
+- It uses the `PUBLIC_KEY` and [discord-interactions package](https://github.com/discord/discord-interactions-js#usage) with a wrapper function (imported from `utils.js`) that makes it conform to [Express's `verify` interface](https://expressjs.com/en/5x/api.html#express.json). This is run on every incoming request to your app.
 - It responds to incoming `PING` requests.
 
 You can learn more about preparing your app to receive interactions in [the interactions documentation](/docs/interactions/overview#preparing-for-interactions).