Skip to content

Refactor sync troubleshooting sections

What does this MR do?

I'm making a few updates to the Troubleshooting Geo synchronization and verification errors doc:

  1. Reintroduce heading changes from !169476 (merged), which I think were lost when two docs were merged into this one
  2. Put registry models in unordered list instead of plaintext code block
  3. Clarify definition of "registry record"
  4. Move Rails console info into each data type section, to make warning more obvious
  5. Add note that Rails console should be opened on secondary site
  6. Adjusted some phrasing about when features were introduced, for consistency
  7. Fixed some placeholder variables that were not encased in <> (per Placeholder text)
  8. Updated mention of issue for a feature that has since been merged, now using the History feature of docs platform

Related issues

Author's checklist

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

  • ~"frontend"
  • ~"backend"
  • ~"type::bug"
  • ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • Ensure a release milestone is set.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.

Merge request reports

Loading