run stylecheck

[bc-devrev]

No description provided.

[github-actions]

Published docs preview URL: https://devrev-preview-ae5b182e-242f-40d8-8054-3fa1fe8b2e0f.docs.buildwithfern.com

[github-actions]

Published docs preview URL: https://devrev-preview-c9134063-8e72-4ea0-8ad9-df669ee80586.docs.buildwithfern.com

[github-actions]

Published docs preview URL: https://devrev-preview-d71d6f8a-c689-477f-8eae-cec381cbe8b6.docs.buildwithfern.com

[bc-devrev]

Suggested change

	- If the item consists of a single word, don't add end punctuation.
	- If the item doesn't include a verb, don't add end punctuation.
	- If the item is entirely in code font, don't add end punctuation.
	- If the item is entirely link text or a document title, don't add end punctuation.
	- Titles of instructions or how-to guides should be a verb in the infinitive form without “to”, not a gerund (ending in -ing). Titles of any other type of section should be noun phrases.
	\ No newline at end of file
	- Titles of instructions or how-to guides should be a verb in the infinitive form without “to”, not a gerund (ending in -ing). Titles of any other type of section should be noun phrases.
	- If the item consists of a single word, don't add end punctuation
	- If the item doesn't include a verb, don't add end punctuation
	- If the item is entirely in code font, don't add end punctuation
	- If the item is entirely link text or a document title, don't add end punctuation
	- Titles of instructions or how-to guides should be a verb in the infinitive form without "to", not a gerund (ending in -ing). Titles of any other type of section should be noun phrases.

[bc-devrev]

✨ Comment from AI reviewer ✨

Since this appears to be the style guide itself, there are relatively few issues to fix. However, I noticed a few items that could be improved for consistency with the rules:

1. The second-level list items under "Instructions or how-to guides" weren't consistently using periods at the end of sentences.
2. The parallel structure in the first bullet list could be improved.
3. Added proper hyphenation for "two-level."

I made suggestions where possible but couldn't add them everywhere. My complete revision is below.

Full text

## Rules

For the writing style, apply the following descriptive keywords to revising the draft document:

- Writing style: authoritative, comprehensive, helpful
- Sentence structure: varied, complex, cohesive
- Vocabulary: consistent, technical
- Grammar and syntax: structured, flawless, articulate
- Description: clear, concise, informative
- Language: standard technical/professional US American English; not British, Indian, or other variants

There are also some very specific style rules that need to be followed:

- Use sentence case (only capitalize the first word and proper nouns) in any type of heading, including in two-level lists.
- Ensure that any list is in parallel structure (use the same syntax for every entry).
- Instructions or how-to guides:
    - They may use two levels; both should be ordered (numbered) lists, not unordered (bulleted) lists.
    - Instructions should be in imperative mood.
    - If there is a location or condition in a step, it should be at the front of the main clause, which must still be in imperative mood.
    - Steps should be more than a single "click"; combine steps if needed to make them more meaningful. If there is an outcome of the step stated, it should be part of the same step, not a new step.
- End each list item with a period or other appropriate sentence-ending punctuation, except in the following cases:
    - If the item consists of a single word, don't add end punctuation
    - If the item doesn't include a verb, don't add end punctuation
    - If the item is entirely in code font, don't add end punctuation
    - If the item is entirely link text or a document title, don't add end punctuation
- Titles of instructions or how-to guides should be a verb in the infinitive form without "to", not a gerund (ending in -ing). Titles of any other type of section should be noun phrases.
- Avoid future tense when describing the behavior of the product. Use simple present instead.

[github-actions]

Published docs preview URL: https://devrev-preview-ca16e3a5-519d-4c9b-ad6e-b6155ecca1f0.docs.buildwithfern.com

[github-actions]

Published docs preview URL: https://devrev-preview-56138f6c-b534-43d6-bd6c-9d8fb7f75a06.docs.buildwithfern.com

[github-actions]

Published docs preview URL: https://devrev-preview-6fd5c8c2-d716-49d4-815e-41c1a57537d6.docs.buildwithfern.com

[github-actions]

Published docs preview URL: https://devrev-preview-3f14609b-0499-4d98-947a-a280991e0165.docs.buildwithfern.com

[github-actions]

Published docs preview URL: https://devrev-preview-375e863c-c3ed-4396-bf75-d8c2d0a21f48.docs.buildwithfern.com

[github-actions]

Published docs preview URL: https://devrev-preview-2f8f3f28-548b-4379-9c08-bcf81a12e0ab.docs.buildwithfern.com

[github-actions]

Published docs preview URL: https://devrev-preview-5f9d4eaf-9835-45df-8454-16bbc459ef99.docs.buildwithfern.com

[github-actions]

Published docs preview URL: https://devrev-preview-1d96e20d-6e12-4a57-8ead-66d79323391d.docs.buildwithfern.com