Recommended: When you add or update
content to an existing project, remember to take these steps: review the style
guide, use checklists, enlist a fellow writer or an editor to copyedit your
work, and request a developmental edit if you feel that it's warranted.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-15 UTC."],[[["Colons are used after introductory phrases that can stand alone as complete sentences to introduce closely-related information like lists."],["The first word after a colon is generally lowercase, with exceptions outlined in the capitalization guidelines."],["Lists introduced by colons should have introductory phrases that form grammatically complete sentences, unlike constructions that simply end with \"are:\"."],["For further guidance on punctuation in introductory material, refer to the sections on list and code-sample introductions."],["To understand the distinctions between colons and dashes, consult the dedicated section on dashes."]]],["Colons signal that related information will follow. When introducing a list, the preceding text must be a complete sentence. The first word after a colon is typically lowercase, though exceptions exist. Examples include: \"Recommended: Tone: concise,\" and \"Recommended: remember to take these steps: review the style guide.\" Colons are also used within run-in headings, and are preferred over dashes in some contexts, and further details regarding introductions are covered in the list and code sample section.\n"]]
