Nomchy/discord.js
1
0
Fork 0
mirror of https://github.com/discordjs/discord.js.git synced 2026-03-09 08:03:30 +01:00
Code Issues Packages Projects Releases Wiki Activity

fix: typos (#11293)

Browse Source
This commit is contained in:
Danial Raza
2025-11-22 11:08:20 +01:00
committed by GitHub
parent 0b12263371
commit 179525d9fc
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
apps/guide/content/docs/legacy/popular-topics/display-components.mdx
View File

@@ -20,7 +20,7 @@ To use the display components, you need to pass the `IsComponentsV2` message fla
## The component `id`
All components can be passed an optional, unique, `id` field holding a 32-bit integer identifier to later identify them in interaction responses. Do not confuse this with the `custom_id` field for interactive components! You can find more information about this [in the discord api documentation](https://discord.com/developers/docs/components/reference#anatomy-of-a-component). Discord will automatically populate the `id` of components that don't have the `id` specified in the payload sequentially starting from `1`. The `id` value `0` is treated as empty. The order components are automatically filled in is an implementation detail and not officially document. If you want to work with the `id` (for example to find and replace the content of a specific component lateron), you should explicitly specify it.
All components can be passed an optional, unique, `id` field holding a 32-bit integer identifier to later identify them in interaction responses. Do not confuse this with the `custom_id` field for interactive components! You can find more information about this [in the discord api documentation](https://discord.com/developers/docs/components/reference#anatomy-of-a-component). Discord will automatically populate the `id` of components that don't have the `id` specified in the payload sequentially starting from `1`. The `id` value `0` is treated as empty. The order components are automatically filled in is an implementation detail and not officially document. If you want to work with the `id` (for example to find and replace the content of a specific component later on), you should explicitly specify it.
In the following sections, we will explain all available display component types in detail and show you some examples on how you can use them.

2
apps/guide/content/docs/legacy/popular-topics/threads.mdx
View File

@@ -93,7 +93,7 @@ const thread = await channel.threads.create({
console.log(`Created thread: ${thread.name}`);
```
They can also be created from an existing message with the `Message#startThread` method, but will be "orphaned" if that message is deleted. The thread is not deleted along with the message and will still be available through the hcannels thread list!
They can also be created from an existing message with the `Message#startThread` method, but will be "orphaned" if that message is deleted. The thread is not deleted along with the message and will still be available through the channels thread list!
```js
// [!code word:startThread]

2
apps/guide/content/docs/voice/audio-resources.mdx
View File

@@ -81,7 +81,7 @@ const resource = createAudioResource('/home/user/voice/music.mp3', {
},
});
// Not recommended - listen to errors from the audio player instead for most usecases!
// Not recommended - listen to errors from the audio player instead for most use cases!
resource.playStream.on('error', (error) => {
console.error('Error:', error.message, 'with track', resource.metadata.title);
});