From 66802fb33a8dd73118b4bec03eed3e2db0a9278f Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Sat, 20 Feb 2021 14:24:57 +0000 Subject: [PATCH] Avoid use of blog form for embargoed content Fixup for commit a425af9915c94c00ce62407affb98154b2a0ecfa. --- sig-docs/blog-subproject/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sig-docs/blog-subproject/README.md b/sig-docs/blog-subproject/README.md index 2373f0952..3a0b33e42 100644 --- a/sig-docs/blog-subproject/README.md +++ b/sig-docs/blog-subproject/README.md @@ -66,7 +66,7 @@ _If a blog post does not contain any technical content (for example, [How You Ca ### Embargoed Content -The blog repository on GitHub is public, therefore any content that needs to remain confidential until a certain time (for example: release posts, security vulnerabilities) should be submitted via the form directly. On [the form](https://docs.google.com/forms/d/e/1FAIpQLSch_phFYMTYlrTDuYziURP6nLMijoXx_f7sLABEU5gWBtxJHQ/viewform), please note the time that the embargo will be lifted. In this case, the editorial team will do all reviews in Google Docs. If this is time sensitive, please email [blog@kubernetes.io](mailto:blog@kubernetes.io). +The blog repository on GitHub is public, therefore any content that needs to remain confidential until a certain time (for example: release posts, security vulnerabilities) should be proposed by email message to [blog@kubernetes.io](mailto:blog@kubernetes.io). In your message, please note the time that the embargo will be lifted. ### SLA