Skip to content

Commit 6a5bd9d

Browse files
authored
remove key words and statement types from example doc (#145)
* remove key words and statement types from example doc * install bigfoot package, which footmisc depends on
1 parent cc5a258 commit 6a5bd9d

File tree

2 files changed

+2
-28
lines changed

2 files changed

+2
-28
lines changed

Dockerfile

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@ RUN npm install --global --unsafe-perm [email protected] [email protected] mermaid-filt
149149
ENV PATH="${PATH}:/usr/local/texlive/bin/aarch64-linux:/usr/local/texlive/bin/x86_64-linux"
150150

151151
# Packages that are needed despite not being used explicitly by the template:
152-
# catchfile, fancyvrb, footmisc, hardwrap, lineno, ltablex, latexmk, needspace, pgf, zref
152+
# bigfoot, catchfile, fancyvrb, footmisc, hardwrap, lineno, ltablex, latexmk, needspace, pgf, zref
153153
RUN tlmgr update --self && tlmgr install \
154154
accsupp \
155155
adjustbox \
@@ -159,6 +159,7 @@ RUN tlmgr update --self && tlmgr install \
159159
adjustbox \
160160
anyfontsize \
161161
appendix \
162+
bigfoot \
162163
bookmark \
163164
booktabs \
164165
caption \

guide.tcg

Lines changed: 0 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -40,33 +40,6 @@ and brands contained herein are the property of their respective owners.
4040

4141
---
4242

43-
# Document Style
44-
45-
**Key Words**
46-
47-
The key words "MUST," "MUST NOT," "REQUIRED," "SHALL," "SHALL NOT," "SHOULD,"
48-
"SHOULD NOT," "RECOMMENDED," "MAY," and "OPTIONAL" in this document's normative
49-
statements are to be interpreted as described in
50-
[RFC 2119: Key words for use in RFCs to Indicate Requirement Levels](https://www.ietf.org/rfc/rfc2119.txt).
51-
52-
**Statement Type**
53-
54-
Please note an important distinction between different sections of text
55-
throughout this document. There are two distinctive kinds of text: _informative
56-
comments_ and _normative statements_. Because most of the text in this
57-
specification will be of the kind _normative statements_, the authors have
58-
informally defined it as the default and, as such, have specifically called out
59-
text of the kind _informative comment_. They have done this by flagging the
60-
beginning and end of each informative comment and highlighting its text in gray.
61-
This means that unless text is specifically marked as of the kind _informative
62-
comment_, it can be considered a _normative statement_.
63-
64-
EXAMPLE:
65-
66-
::: Informative ::::
67-
Reach out to <admin@trustedcomputinggroup> with any questions about this document.
68-
::::::::::::::::::::
69-
7043
\tableofcontents
7144

7245
\listoftables

0 commit comments

Comments
 (0)