Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos #303

Merged
merged 1 commit into from
Jan 19, 2025
Merged

Fix typos #303

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 15 additions & 15 deletions doc/main.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@ <h3>General</h3>
</figure>

<p>The <code>smpte.js</code> script contains the code that renders the HTML document provided by the author into an HTML
document approprtiate for publication. This rendering happens automatically when loading the document in a web browser.</p>
document appropriate for publication. This rendering happens automatically when loading the document in a web browser.</p>

</section>

Expand Down Expand Up @@ -433,7 +433,7 @@ <h4>Foreword section</h4>

<div class="example">
<pre>&lt;section id=&quot;sec-foreword&quot;&gt;
&lt;p&gt;This is the additional infomation relevant to the document.&lt;/p&gt;
&lt;p&gt;This is the additional information relevant to the document.&lt;/p&gt;
&lt;/section&gt;
</pre>
</div>
Expand Down Expand Up @@ -522,7 +522,7 @@ <h4>Normative references section</h4>
be used when citing the reference in the prose.</li>
<li>The <code>cite</code> element shall contain an <code>id</code> attribute with value prefixed by
<code>bib-</code>.</li>
<li>Each <code>li</code> element may contain additional title infomation.
<li>Each <code>li</code> element may contain additional title information.
<li>Each <code>li</code> element may contain one <code>a</code> element that contains a location where the reference can
be retrieved.</li>
</ul>
Expand Down Expand Up @@ -570,7 +570,7 @@ <h4>Terms and definitions section</h4>
<li>The <code>id</code> attribute of the <code>dl</code> element shall be equal to <code>terms-int-defs</code>.</li>
<li>Each <code>dt</code> element contains a single term, abbreviation or symbol. Zero or more additional <code>dt</code> elements
can follow the first <code>dt</code> element, in which case all the terms, abbreviations and symbols in the immediately
preceding <code>dt</code> elements are synomys.</li>
preceding <code>dt</code> elements are synonyms.</li>
<li>The first <code>dd</code> element immediately following the last <code>dt</code> element, if present, shall be
a definition.</li>
<li>The next <code>dd</code> element, if present, shall contain a single reference to a bibliographic entry,
Expand Down Expand Up @@ -649,13 +649,13 @@ <h4>Annex section(s)</h4>
<p>An <a>Annex section</a> shall not contain nested <a>annex sections</a>.</p>

<div class="example">
<pre>&lt;section class=&quot;annex&quot; id=&quot;sec-addtional-info&quot;&gt;
<pre>&lt;section class=&quot;annex&quot; id=&quot;sec-additional-info&quot;&gt;
&lt;h2&gt;Additional Info&lt;/h2&gt;
&lt;section id=&quot;sec-addtional-info-sub-section&quot;&gt;
&lt;section id=&quot;sec-additional-info-sub-section&quot;&gt;
&lt;h3&gt;Additional Info Sub Section&lt;/h3&gt;
&lt;p&gt;Some technical content&lt;/p&gt;
&lt;/section&gt;
&lt;section id=&quot;sec-addtional-info-sub-section-more&quot;&gt;
&lt;section id=&quot;sec-additional-info-sub-section-more&quot;&gt;
&lt;h3&gt;Additional Info Sub Section More&lt;/h3&gt;
&lt;p&gt;Some technical content&lt;/p&gt;
&lt;/section&gt;
Expand Down Expand Up @@ -711,7 +711,7 @@ <h4>Additional elements section</h4>
<pre>&lt;section id=&quot;sec-elements&quot;&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;a id=&quot;element-sample-text&quot; title=&quot;Description of the elemnent&quot; href=&quot;./elements/form.docx&quot;&gt;&lt;/a&gt;
&lt;a id=&quot;element-sample-text&quot; title=&quot;Description of the element&quot; href=&quot;./elements/form.docx&quot;&gt;&lt;/a&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;/section&gt;</pre>
Expand Down Expand Up @@ -884,7 +884,7 @@ <h4>Lists of key-value pairs</h4>
<section id="sec-list-element">
<h4>Lists</h4>

<p>A list can be inserted using either an <code>ol</code> or <code>ul</code> element. The <code>ul</code> (unordered list) element should be used when the order of listed items is not meaniful or important. The <code>ol</code> (ordered list) element should be only used when the order of listed items is meaningful and/or important to the list and/or document.</p>
<p>A list can be inserted using either an <code>ol</code> or <code>ul</code> element. The <code>ul</code> (unordered list) element should be used when the order of listed items is not meaningful or important. The <code>ol</code> (ordered list) element should be only used when the order of listed items is meaningful and/or important to the list and/or document.</p>

<p>
General guidelines for lists:
Expand Down Expand Up @@ -1517,7 +1517,7 @@ <h4>Column Alignment</h4>
</table>

<p class="note">
Classes are available to center align columns 1-8 (as <code>col-x-center</code>), and mutliple classes to <code>table</code> may be added to align more columns as needed.
Classes are available to center align columns 1-8 (as <code>col-x-center</code>), and multiple classes to <code>table</code> may be added to align more columns as needed.
</p>
<p class="note">
Tables over 8 columns wide should not be used and instead split into multiple smaller tables.
Expand Down Expand Up @@ -1892,7 +1892,7 @@ <h4>List <code>type</code> Examples</h4>
<h3>List Nesting</h3>

<p>
Both <code>ol</code> and <code>ul</code> elements may be nexted as many times within a <code>li</code> element as needed to achieve the required results. See below for various examples.
Both <code>ol</code> and <code>ul</code> elements may be nested as many times within a <code>li</code> element as needed to achieve the required results. See below for various examples.
</p>

<div class="example">
Expand Down Expand Up @@ -2058,7 +2058,7 @@ <h3>Mapping <code>pubState</code> and <code>pubStage</code> to Document Status</
</thead>
<tbody>
<tr>
<td>Undergoing intial draft or revision in DG/SG/WG</td>
<td>Undergoing initial draft or revision in DG/SG/WG</td>
<td><code>WD</code></td>
<td><code>draft</code></td>
</tr>
Expand Down Expand Up @@ -2148,7 +2148,7 @@ <h3>Sample Workflow </h3>

<li>Project is approved
<ol type="a">
<li>If document is an intial draft, skip to Workflow Step (2)</li>
<li>If document is an initial draft, skip to Workflow Step (2)</li>
<li>If document is a revision, skip to Workflow Step (3)</li>
</ol>
</li>
Expand Down Expand Up @@ -2195,7 +2195,7 @@ <h3>Sample Workflow </h3>
<li>Document is updated in PR to <code>&lt;meta itemprop="pubState" content="pub" /&gt;</code>, <code>&lt;meta itemprop="pubStage" content="WD" /&gt;</code> and <code>&lt;meta itemprop="pubDateTime" content="2023-04-15" /&gt;</code> (assumed date of completion).</li>
<li>PR is approved by document editor and DG chair. PR is merged to <code>main</code>.</li>
<li>A release is created targeted at <code>main</code> named <code>20230415-wd</code> with a tag of the same name.</li>
<li>The tooling creates the zip needed for TC 2-week preFCD review, with redlines against lastest edition and/or last draft (if applicable)</li>
<li>The tooling creates the zip needed for TC 2-week preFCD review, with redlines against latest edition and/or last draft (if applicable)</li>
<li>ZIP is sent to TC for 2-week preFCD review</li>
<li>Continue to Workflow Step (6)</li>
</ol>
Expand Down Expand Up @@ -2230,7 +2230,7 @@ <h3>Sample Workflow </h3>
<li>PR is merged to <code>main</code>.</li>
<li>A release is created targeted at <code>main</code> named <code>20230415-cd1</code> (or <code>20230515-cd1</code> if Workflow Step 7 was used) with a tag of the same name.</li>
<li>If document is to continue to FCD ballot, the ZIP file that is generated by the tooling in <code>main</code> with required redlines is sent to the TC for FCD ballot. Skip to Workflow Step (9)</li>
<li>If document is to undergo a PCD period, the contents in the ZIP file generated by the tooling in <code>main</code> are used for the PCD. After PCD period ends, go back to Workflow Step (6). See <a href="#sec-document-github-releases"></a> for itterative CD naming. </li>
<li>If document is to undergo a PCD period, the contents in the ZIP file generated by the tooling in <code>main</code> are used for the PCD. After PCD period ends, go back to Workflow Step (6). See <a href="#sec-document-github-releases"></a> for iterative CD naming. </li>
<li>Continue to Workflow Step (9)</li>
</ol>
</li>
Expand Down
Loading