Skip to content

Commit 92ed1e0

Browse files
jorge-campocheny0
andauthored
Update prompts/conversion/markdown-to-json/procedure-template.md
Co-authored-by: cheny0 <67916832+cheny0@users.noreply.github.com>
1 parent 4b5291d commit 92ed1e0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

prompts/conversion/markdown-to-json/procedure-template.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ This note-type callout is exclusively to alert readers about what roles, permiss
9191
- Keep each callout concise (≤ 2 short sentences). If the content needs a list or multiple paragraphs, move it into the body under a heading. <!-- PROC-BEHAV-CALLOUTS-CONCISE -->
9292
- Ensure the callout content is directly relevant to the nearby task or decision point. <!-- PROC-BEHAV-CALLOUTS-RELEVANT -->
9393
- Use the appropriate type: `Tip`, `Note`, `Important`, or `Caution`. <!-- PROC-BEHAV-CALLOUTS-TYPE -->
94-
- Do **not** include full procedural steps or long prerequisite checklists inside callouts. Put steps in the main flow; keep prerequisite lists in Before you start. <!-- PROC-BEHAV-CALLOUTS-NO-STEPS -->
94+
- Do **not** include full procedural steps or long prerequisite checklists inside callouts. Put steps in the main flow; keep prerequisite lists in "Before you start." <!-- PROC-BEHAV-CALLOUTS-NO-STEPS -->
9595
- For the allowed callout types and when to use them, see the [writing rules](../../3-validating-design/writing-rules/README.md). <!-- PROC-BEHAV-CALLOUTS-TYPES-REFER-STYLEGUIDE -->
9696

9797
**Example:**

0 commit comments

Comments
 (0)