From 328ea9ba8f69b6a853fa7f8ff20d81b2ca0f3330 Mon Sep 17 00:00:00 2001 From: James Sorrenti Date: Tue, 11 Nov 2025 17:32:41 -0500 Subject: [PATCH] Format headings for consistency in communications.md (#35569) --- handbook/company/communications.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/handbook/company/communications.md b/handbook/company/communications.md index e3ae7f1cde..b23205fafb 100644 --- a/handbook/company/communications.md +++ b/handbook/company/communications.md @@ -1090,12 +1090,12 @@ Headings and titles should: ##### Static headings -Use static headings (a `noun` or `noun phrase`) e.g., “Log destinations,” for concept or reference topics. Be as short and specific as possible. +Use static headings (a `noun` or `noun phrase`) e.g., _“Log destinations,”_ for concept or reference topics. Be as short and specific as possible. ##### Task-based headings -Use task-based headings (`verb` + `topic`) e.g., _“Configure a log destination”_ for guides and tutorials where the heading should reveal the task that the reader is trying to achieve. +Use task-based headings (`verb` + `topic`) e.g., _“Configure a log destination,”_ for guides and tutorials where the heading should reveal the task that the reader is trying to achieve. ##### Avoid _-ing_ verb forms in headings