Repository navigation
Explain messenger installation and personal login step by step - #127
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Telegram and MAX installation guides led with package terminology and left account confirmation unclear. Start with four reader steps: open the agent, copy the installation request, confirm login personally and check the connected account and chats.
Explain Telegram connection registration separately from QR account login, where to find the phone scanner, hidden password input and browser/phone alternatives. Explain MAX QR login and browser alternatives. Include a direct terminal command when the agent cannot offer interactive input. Keep the existing installation/copy components, typography, native technical references and incoming anchors. Render the same steps and request in HTML and Markdown in EN/RU/ES.
Validation: production build, lint, typecheck, shared standards, strict documentation checks, links and SEO passed. All 24 targeted production browser cases and the timing-headroom guard passed. Checked clipboard/mobile layout on both RU guides and MAX mobile accessibility. No live account actions.