Skip to content

Commit f4a7f81

Browse files
committed
[clang-format][doc] Minor cleanup
1 parent 5b4445e commit f4a7f81

File tree

2 files changed

+4
-3
lines changed

2 files changed

+4
-3
lines changed

clang/docs/ClangFormatStyleOptions.rst

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5117,7 +5117,7 @@ the configuration (without a prefix: ``Auto``).
51175117

51185118
.. note::
51195119

5120-
It must contain ``type``.
5120+
It **must** contain ``type``.
51215121

51225122
Items to the left of ``type`` will be placed to the left of the type and
51235123
aligned in the order supplied. Items to the right of ``type`` will be
@@ -6410,6 +6410,7 @@ the configuration (without a prefix: ``Auto``).
64106410
64116411
TableGenBreakInsideDAGArg: BreakAll
64126412
TableGenBreakingDAGArgOperators: [ins, outs]
6413+
64136414
makes the line break only occurs inside DAGArgs beginning with the
64146415
specified identifiers ``ins`` and ``outs``.
64156416

@@ -6537,7 +6538,7 @@ The goal of the clang-format project is more on the side of supporting a
65376538
limited set of styles really well as opposed to supporting every single style
65386539
used by a codebase somewhere in the wild. Of course, we do want to support all
65396540
major projects and thus have established the following bar for adding style
6540-
options. Each new style option must ..
6541+
options. Each new style option must:
65416542

65426543
* be used in a project of significant size (have dozens of contributors)
65436544
* have a publicly accessible style guide

clang/include/clang/Format/Format.h

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3650,7 +3650,7 @@ struct FormatStyle {
36503650
/// * type
36513651
///
36523652
/// \note
3653-
/// It \b must contain ``type``.
3653+
/// It **must** contain ``type``.
36543654
/// \endnote
36553655
///
36563656
/// Items to the left of ``type`` will be placed to the left of the type and

0 commit comments

Comments
 (0)