diff --git a/frontend/apps/remark42/app/components/profile/profile.spec.tsx b/frontend/apps/remark42/app/components/profile/profile.spec.tsx
index 0cb3a1b5..b888bb87 100644
--- a/frontend/apps/remark42/app/components/profile/profile.spec.tsx
+++ b/frontend/apps/remark42/app/components/profile/profile.spec.tsx
@@ -164,7 +164,7 @@ describe('', () => {
expect(container.querySelector('profile-footer')).not.toBeInTheDocument();
});
- it('load more button should dissapear if there no more comments to fetch', async () => {
+ it('load more button should disappear if there no more comments to fetch', async () => {
jest
.spyOn(api, 'getUserComments')
.mockImplementation(async () => ({ comments: new Array(10).fill(commentStub), count: 15 }));
diff --git a/frontend/apps/remark42/app/profile.ts b/frontend/apps/remark42/app/profile.ts
index ccdd8fc8..15adc4c1 100644
--- a/frontend/apps/remark42/app/profile.ts
+++ b/frontend/apps/remark42/app/profile.ts
@@ -58,7 +58,7 @@ function animateDisappear(): Promise {
if (!root || !iframe) {
return;
}
- setStyles(root, styles.rootDissapear);
+ setStyles(root, styles.rootDisappear);
root.addEventListener('transitionend', handleTransitionEnd);
});
});
@@ -111,7 +111,7 @@ const styles = {
rootAppear: {
opacity: '1',
},
- rootDissapear: {
+ rootDisappear: {
opacity: '0',
transition: 'opacity 0.3s ease-out',
},
diff --git a/site/src/docs/configuration/telegram/index.md b/site/src/docs/configuration/telegram/index.md
index d892cc16..75d6740e 100644
--- a/site/src/docs/configuration/telegram/index.md
+++ b/site/src/docs/configuration/telegram/index.md
@@ -48,11 +48,24 @@ To enable Telegram authentication for the users, set the variable `AUTH_TELEGRAM
To integrate notifications about any comment on your sites with remark42 with [Telegram](https://telegram.org)
1. Set `NOTIFY_ADMINS=telegram`
-2. Make [a channel](https://telegram.org/faq_channels), **add your bot as Administrator** into it and add channel ID to remark42 configuration as `NOTIFY_TELEGRAM_CHAN`
+2. Set up your notification destination and add its ID to remark42 configuration as `NOTIFY_TELEGRAM_CHAN`
- - "Post messages" permission is enough for bot to be able to post messages in your channel, others are unnecessary;
- - To obtain a public channel ID, forward any message from it to [@JsonDumpBot](https://t.me/JsonDumpBot): look for `id` in `forward_from_chat`;
- - If you want to use a private channel or chat, use [these instructions](https://github.com/GabrielRF/telegram-id#web-channel-id) to obtain the ID.
+ Notifications can be sent to:
+ - **Channels**: Create [a channel](https://telegram.org/faq_channels) and **add your bot as Administrator**
+ - **Groups**: Create a group and add your bot to it
+ - **Individual users**: Use the user's Telegram ID
+
+ For the ID, you can use:
+ - **Public channels/groups**: Use the username without the @ symbol (e.g., `mygroup` instead of `@mygroup`)
+ - **Private channels/groups**: Use the numeric ID
+ - **Users**: Use the user's numeric Telegram ID
+
+ To obtain IDs:
+ - For public channel/group ID: Forward any message from it to [@JsonDumpBot](https://t.me/JsonDumpBot) and look for `id` in `forward_from_chat`
+ - For private channels/groups: Use [these instructions](https://github.com/GabrielRF/telegram-id#web-channel-id) or [@myidbot](https://t.me/myidbot)
+ - For user ID: Users can get their ID from [@myidbot](https://t.me/myidbot)
+
+ Note: When using channels or groups, ensure the bot has "Post messages" permission.
### Notifications for users
diff --git a/site/src/docs/contributing/api/index.md b/site/src/docs/contributing/api/index.md
index b0b5e871..1dc09725 100644
--- a/site/src/docs/contributing/api/index.md
+++ b/site/src/docs/contributing/api/index.md
@@ -139,7 +139,7 @@ type Config struct {
Not available
Streaming API supposed to provide server-sent events for post updates as well as a site update:
-- `GET /api/v1/stream/info?site=site-idd&url=post-url&since=unix_ts_msec` - returns stream (`event: info`) with `PostInfo` records for the site and URL. `since` is optional
+- `GET /api/v1/stream/info?site=site-id&url=post-url&since=unix_ts_msec` - returns stream (`event: info`) with `PostInfo` records for the site and URL. `since` is optional
- `GET /api/v1/stream/last?site=site-id&since=unix_ts_msec` - returns updates stream (`event: last`) with comments for the site, `since` is optional
It was removed in https://github.com/umputun/remark42/pull/826 due to not being used and affecting tests flakiness and could be returned if there will be a developer who would be willing to write frontend support for it.