docs(1secure): clarify when New status changes to Healthy

[james-s-anderson]

Updates the note under the diagram on the Statuses page: the New status changes to Healthy when the first batch of data arrives from the environment without error. Removes the sentence about how long the change can take.

Generated with AI

Co-Authored-By: Claude Code ai@netwrix.com

[github-actions]

Documentation PR Review

Editorial Review

docs/1secure/admin/statuses.md

• Completeness — Lines 16–17: The earlier note told readers how long the change from New to Healthy can take (from about a minute to several hours, depending on environment size), and this edit removes that. Without it, readers can't tell whether a source that has shown New for an hour is still working normally or has a problem. If the time frame still holds, keep it. Suggested fix: "The New status changes to Healthy when the first batch of data arrives from the environment without error. This can take from about a minute to several hours, depending on the size of the environment."
• Completeness — Line 17: "without error" suggests the status can change to something other than Healthy, but the note doesn't say what happens if the first batch of data has errors. The statuses are listed only in an image, so readers can't easily look up the other status as text. Suggested fix: add a sentence that names the resulting status, for example: "If the data contains errors, the status changes to <status-name>." Replace <status-name> with the status the product actually shows.

Summary

2 editorial suggestions across 1 file. Vale and Dale issues are auto-fixed separately.

---

What to do next:

Comment @claude on this PR followed by your instructions to get help:

• @claude fix all issues — fix all editorial issues
• @claude help improve the flow of this document — get writing assistance
• @claude explain the voice issues — understand why something was flagged

You can ask Claude anything about the review or about Netwrix writing standards.

Automated fixes are only available for branches in this repository, not forks.

[github-actions]

Auto-Fix Summary

0 issues fixed, 0 skipped across 1 files

Ask @claude on this PR if you'd like an explanation of any fix.