Skip to content

spaces in low-level-settings.md#855

Merged
an-martynova merged 1 commit intomasterfrom
an-martynova-patch-2
Apr 14, 2026
Merged

spaces in low-level-settings.md#855
an-martynova merged 1 commit intomasterfrom
an-martynova-patch-2

Conversation

@an-martynova
Copy link
Copy Markdown
Contributor

space removed, now expecting a correct presentation on the page

@an-martynova an-martynova self-assigned this Apr 14, 2026
@github-actions
Copy link
Copy Markdown

Preview was deployed to: https://pull-request-855.kb-adg.pages.dev/

@an-martynova an-martynova requested review from adbuker and removed request for el-termikael April 14, 2026 13:12
@@ -113,7 +113,7 @@ Host: example.org`
will be converted to

`GET /foo/bar/ HTTP/1.1
Copy link
Copy Markdown

@owlsy owlsy Apr 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just using two regular spaces will not correctly show on the page (it will just show one space).

We should ensure the spaces between GET and /foo/bar/ are using the Unicode em space (8195 in UTF-8).

Markdown code:

`GET  /foo/bar/ HTTP/1.1
Host:example.org`

@an-martynova an-martynova merged commit febf82f into master Apr 14, 2026
4 checks passed
@an-martynova an-martynova deleted the an-martynova-patch-2 branch April 14, 2026 18:52
owlsy added a commit to owlsy/KnowledgeBase that referenced this pull request Apr 14, 2026
As mentioned several times in AdguardTeam#848, AdguardTeam#853, and AdguardTeam#855, just using two regular spaces will not correctly show on the page. It will just show one space.

The second space between GET and /foo/bar/ should be using the Unicode em space (8195 in UTF-8) to resolve this.
owlsy added a commit to owlsy/KnowledgeBase that referenced this pull request Apr 14, 2026
As mentioned several times in AdguardTeam#848, AdguardTeam#853, and AdguardTeam#855, just using two regular spaces continues to not show correctly on the page. It just shows one space.

The second space between GET and /foo/bar/ should be using the Unicode em space (8195 in UTF-8).

Creating a PR myself to resolve this, as I have been ignored.

Closes AdguardTeam#853.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants