| Index: sky/specs/style-guide.md
|
| diff --git a/sky/specs/style-guide.md b/sky/specs/style-guide.md
|
| index 123acd453eb91acbb0b43a1dbd59332dd9ccc1d1..e475fa810ab17d3ea8e5dda1654d6f24adfea61b 100644
|
| --- a/sky/specs/style-guide.md
|
| +++ b/sky/specs/style-guide.md
|
| @@ -87,16 +87,16 @@ the expression, even if it is short. (Doing so makes it unobvious that
|
| there is relevant code there. This is especially important for early
|
| returns.)
|
|
|
| -If a flow control structure has just one statement, then don't use
|
| -braces around it except where doing so would help readability or avoid
|
| -the dangling-else problem. Keeping the code free of boilerplate or
|
| -redundant punctuation keeps it concise and readable.
|
| +If a flow control structure's statement is one line long, then don't
|
| +use braces around it. (Keeping the code free of boilerplate or
|
| +redundant punctuation keeps it concise and readable.)
|
|
|
| > For example,
|
| > ```dart
|
| -> if (children != null)
|
| +> if (children != null) {
|
| > for (RenderBox child in children)
|
| > add(child);
|
| +> }
|
| > ```
|
| > ...rather than:
|
| > ```dart
|
|
|