From 5e4c31272594ef3ac37d0ee6199176b5f3c6a294 Mon Sep 17 00:00:00 2001 From: Vaibhav Date: Tue, 16 Aug 2022 17:23:00 +0530 Subject: Corrected the README link --- sig-node/sig-node-contributor-ladder.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'sig-node') diff --git a/sig-node/sig-node-contributor-ladder.md b/sig-node/sig-node-contributor-ladder.md index 78833917..b961a25e 100644 --- a/sig-node/sig-node-contributor-ladder.md +++ b/sig-node/sig-node-contributor-ladder.md @@ -13,7 +13,7 @@ If you are a community member that wants to suggest changes, please do! SIG Node welcomes new contributors to the community, help is always desired. Not all contributors are able to provide sustained contribution, but each contribution is always welcome. This document intends to capture a leadership path for contributors that intend to provide a sustained contribution to the SIG and its associated code base by taking on reviewer and approver responsibilities at various levels. -Please review the list of [sub-projects](./README.mdmd#subprojects) for areas to engage! +Please review the list of [sub-projects](./README.md#subprojects) for areas to engage! ## SIG Node reviewers and approvers @@ -113,4 +113,4 @@ There are different ways to earn trust: - Actively triage issues and PRs, provide support to contributors to drive their PRs to completion. **Be present** -Participate in SIG Node meetings by speaking about KEPs or improvements driven, or find some other way to prove the identity behind GitHub handle. \ No newline at end of file +Participate in SIG Node meetings by speaking about KEPs or improvements driven, or find some other way to prove the identity behind GitHub handle. -- cgit v1.2.3