Skip to content

Commit 179525d

Browse files
authored
fix: typos (#11293)
1 parent 0b12263 commit 179525d

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ To use the display components, you need to pass the `IsComponentsV2` message fla
2020

2121
## The component `id`
2222

23-
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.
23+
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.
2424

2525
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.
2626

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ const thread = await channel.threads.create({
9393
console.log(`Created thread: ${thread.name}`);
9494
```
9595

96-
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!
96+
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!
9797

9898
```js
9999
// [!code word:startThread]

apps/guide/content/docs/voice/audio-resources.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ const resource = createAudioResource('/home/user/voice/music.mp3', {
8181
},
8282
});
8383

84-
// Not recommended - listen to errors from the audio player instead for most usecases!
84+
// Not recommended - listen to errors from the audio player instead for most use cases!
8585
resource.playStream.on('error', (error) => {
8686
console.error('Error:', error.message, 'with track', resource.metadata.title);
8787
});

0 commit comments

Comments
 (0)