Skip to content

Markdown fix #195

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

Markdown fix #195

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
2 changes: 1 addition & 1 deletion howto-conduct-a-privacy-review.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,7 @@ is done in several steps.
privacy-request repo keeps track of privacy review requests we receive, but
the substance of those reviews (i.e., the issues that need to be addressed
in the proposed spec) must be filed in the repo for the proposed spec.
For example, [privacy request #56]([Review #56](https://github.com/w3cping/privacy-request/issues/56)
For example, [privacy request #56](https://github.com/w3cping/privacy-request/issues/56)
is an issue in PING's privacy-request repo, but issues resulting for the review
should be filed in the [Secure Payment Confirmation repo](https://github.com/w3c/secure-payment-confirmation/issues).)

Expand Down