From 15cdab543bb269082af06fec8188b4147d2f8559 Mon Sep 17 00:00:00 2001 From: Fuqiao Xue Date: Fri, 11 Oct 2024 16:12:50 +0800 Subject: [PATCH] Markdown fix --- howto-conduct-a-privacy-review.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/howto-conduct-a-privacy-review.md b/howto-conduct-a-privacy-review.md index ce753d3..09c29dc 100644 --- a/howto-conduct-a-privacy-review.md +++ b/howto-conduct-a-privacy-review.md @@ -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).)