Skip to content

Fix typos #124

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix typos #124

Show file tree
Hide file tree
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
8 changes: 4 additions & 4 deletions .github/workflows/codeql.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,18 +24,18 @@ jobs:

steps:
- name: Checkout
uses: actions/checkout@v3
uses: actions/checkout@v5

- name: Initialize CodeQL
uses: github/codeql-action/init@v2
uses: github/codeql-action/init@v3
with:
languages: ${{ matrix.language }}
queries: +security-and-quality

- name: Autobuild
uses: github/codeql-action/autobuild@v2
uses: github/codeql-action/autobuild@v3

- name: Perform CodeQL Analysis
uses: github/codeql-action/analyze@v2
uses: github/codeql-action/analyze@v3
with:
category: "/language:${{ matrix.language }}"
2 changes: 1 addition & 1 deletion public/spec.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -151,7 +151,7 @@ <h3><span class="spec-secid" title="link to this section"><a href="#sec-Block-fo
</section>
<section id="sec-Inline-form" secid="1.4.2">
<h3><span class="spec-secid" title="link to this section"><a href="#sec-Inline-form">1.4.2</a></span>Inline form</h3>
<p>When the <span class="spec-ref"><a href="#opening-tag" data-name="opening-tag">opening tag</a></span> and <span class="spec-ref"><a href="#closing-tag" data-name="closing-tag">closing tag</a></span> appear on the same line within a paragrah, the tag should be treated as an inline document elmement nested inside of the block-level paragraph element:</p>
<p>When the <span class="spec-ref"><a href="#opening-tag" data-name="opening-tag">opening tag</a></span> and <span class="spec-ref"><a href="#closing-tag" data-name="closing-tag">closing tag</a></span> appear on the same line within a paragraph, the tag should be treated as an inline document element nested inside of the block-level paragraph element:</p>
<pre id="example-15c64" class="spec-example"><a href="#example-15c64">Example № 5</a><code>This is a paragraph {% foo %}that contains a tag{% /foo %}
</code></pre>
<p>When the <span class="spec-ref"><a href="#opening-tag" data-name="opening-tag">opening tag</a></span> and <span class="spec-ref"><a href="#closing-tag" data-name="closing-tag">closing tag</a></span> appear on the same line with no other surrounding content, the tag should still be treated as an inline document element, nested within an implied block-level paragraph element:</p>
Expand Down
2 changes: 1 addition & 1 deletion spec/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,7 @@ This is content inside of a block-level tag

### Inline form

When the *opening tag* and *closing tag* appear on the same line within a paragrah, the tag should be treated as an inline document elmement nested inside of the block-level paragraph element:
When the *opening tag* and *closing tag* appear on the same line within a paragraph, the tag should be treated as an inline document element nested inside of the block-level paragraph element:

```example
This is a paragraph {% foo %}that contains a tag{% /foo %}
Expand Down