Skip to content

Commit fd9ae62

Browse files
committed
Prettier
1 parent ceef196 commit fd9ae62

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

BLOG_STYLE_GUIDE.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Welcome to the GraphQL Blog Style Guide! This document outlines best practices a
88

99
## ✍️ General Writing Principles
1010

11-
- **Audience First**: Think about who the audience of your post is.
11+
- **Audience First**: Think about who the audience of your post is.
1212
- **Clarity is Key**: Prioritize clear, concise explanations over jargon. Break down complex ideas with examples.
1313
- **Vendor neutral**: The GraphQL Blog is about GraphQL as a technology. Vendor specific content and personal promotion doesn't belong in the GraphQL blog.
1414

@@ -43,9 +43,9 @@ This list is non-exhaustive. If there is something you would like to see on the
4343
### Introduction
4444

4545
- Hook the reader in 1–2 sentences.
46-
- Set clear expectations about what the post covers and who it's for:
47-
- open source users of a given project (release notes, updates,...) are probably already familiar with the tool.
48-
- technical users (best practices, working group updates) have a technical background but may be new to GraphQL concepts.
46+
- Set clear expectations about what the post covers and who it's for:
47+
- open source users of a given project (release notes, updates,...) are probably already familiar with the tool.
48+
- technical users (best practices, working group updates) have a technical background but may be new to GraphQL concepts.
4949
- larger audience (case studies, events, grants, reports) may not necessarily have a technical background but still be interested in latest GraphQL content.
5050

5151
### Body

0 commit comments

Comments
 (0)