docs(notebooks): update FAQ to describe conflict resolution modal#16879
Open
inkeep[bot] wants to merge 1 commit into
Open
docs(notebooks): update FAQ to describe conflict resolution modal#16879inkeep[bot] wants to merge 1 commit into
inkeep[bot] wants to merge 1 commit into
Conversation
Contributor
Deploy preview
|
Contributor
|
Vale prose linter → found 0 errors, 31 warnings, 0 suggestions in your markdown Full report → Copy the linter results into an LLM to batch-fix issues. Linter being weird? Update the rules!
|
| Line | Severity | Message | Rule |
|---|---|---|---|
| 14:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 16:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 18:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 20:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 22:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 24:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 26:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 28:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 30:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 32:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 34:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 36:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 38:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 40:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 42:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 44:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 46:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 48:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 50:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 52:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 54:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 56:54 | warning | Use 'PostHog' instead of 'posthog'. | Vale.Terms |
| 144:166 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 153:62 | warning | Use bold (text) for UI elements, not quotes. | PostHogDocs.UIBoldNotQuotes |
| 153:155 | warning | Capitalize 'Session Replay' for PostHog's product. Use 'session replay' for the general industry concept. | PostHogBase.ProductNames |
| 153:205 | warning | Capitalize 'Logs' for PostHog's product. Use 'logs' for the general industry concept. | PostHogBase.ProductNames |
| 162:5 | warning | 'Feature flags' heading should be in sentence case, and product names should be capitalized. | PostHogBase.SentenceCase |
| 162:5 | warning | Capitalize 'Feature Flags' for PostHog's product. Use 'Feature flags' for the general industry concept. | PostHogBase.ProductNames |
| 166:166 | warning | Capitalize 'Surveys' for PostHog's product. Use 'surveys' for the general industry concept. | PostHogBase.ProductNames |
| 210:93 | warning | Avoid trivializing words. 'easily' can sound dismissive to the reader. | PostHogDocs.Trivializers |
| 210:128 | warning | Use American English. Use 'organization' instead of 'organisation'. | PostHogBase.AmericanEnglish |
Contributor
|
Hey @a-lider! This docs PR was generated for you by an agent. You're responsible for reviewing and merging it into production.
|
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
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.
Changes
Updates the Notebooks FAQ section to document the new conflict resolution modal introduced in PostHog/posthog#58213.
What's updated
FAQ: "Do notebooks support real-time multiplayer editing?"
The previous answer mentioned conflict detection but was vague about what users experience. The updated answer now describes:
Why
PR #58213 added a new conflict resolution UI for collaborative notebook editing. When sync conflicts occur (due to stale streams or rebase failures), users now see a helpful modal with clear recovery options instead of a generic warning. The docs should reflect this improved experience.
Closes: PostHog/posthog#58213
cc @a-lider for review
This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.