summaryrefslogtreecommitdiff
path: root/communication
diff options
context:
space:
mode:
authorNitishKumar06 <justnitish06@gmail.com>2023-02-01 08:05:27 +0530
committerNitishKumar06 <justnitish06@gmail.com>2023-02-01 08:05:27 +0530
commit215b4b5b0fe7b9fe9c8412fc30de74b14ab03f60 (patch)
tree4c8e9a500012b1843dface165d30f113d49decff /communication
parente574f7a4fe4e9185a181551b49a9363d11c6582f (diff)
FIX: Broken Link on Comms Role-hadbooks
Diffstat (limited to 'communication')
-rw-r--r--communication/contributor-comms/role-handbooks/storytellers.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/communication/contributor-comms/role-handbooks/storytellers.md b/communication/contributor-comms/role-handbooks/storytellers.md
index c65a0a01..a90f72de 100644
--- a/communication/contributor-comms/role-handbooks/storytellers.md
+++ b/communication/contributor-comms/role-handbooks/storytellers.md
@@ -33,7 +33,7 @@ There are multiple ways to successfully contribute a Kubernetes blog post. Here
* Connect with a storyteller -- if you reach out to Contributor Comms, you will be paired with someone to help you through writing, editing, and getting your article published
* Discussion happens via GitHub issue or through working group meetings
* This includes working with Contributor Comms team to polish, and format your blog post
- * There is not a single canonical format for documents, but we do have [guidelines for effective articles](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/blog-guidelines.md#how-to-write-an-effective-blog)
+ * There is not a single canonical format for documents, but we do have [guidelines for effective articles](https://github.com/kubernetes/community/tree/master/sig-docs/blog-subproject#blog-guidelines)
* There are further technical considerations by the [Blog team](https://github.com/kubernetes/community/blob/4026287dc3a2d16762353b62ca2fe4b80682960a/sig-docs/blog-subproject/README.md#submit-a-post)
When it's ready, submit the blog post: