From 430178c55b354bc77232b546f4c1e15d636b8a70 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Oskar=20Thor=C3=A9n?= Date: Fri, 27 Nov 2020 18:55:11 +0800 Subject: [PATCH] Minor fixes to RFC 1 (#261) Dead link and wrong domain in yaml header --- content/docs/rfcs/1/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/rfcs/1/README.md b/content/docs/rfcs/1/README.md index 08751eea..eb957b3f 100644 --- a/content/docs/rfcs/1/README.md +++ b/content/docs/rfcs/1/README.md @@ -1,5 +1,5 @@ --- -domain: rfc.unprotocols.org +domain: rfc.vac.dev shortname: 1/COSS name: Consensus-Oriented Specification System status: draft @@ -81,7 +81,7 @@ Every specification has an independent lifecycle that documents clearly its curr A specification has six possible states that reflect its maturity and contractual weight: -![Lifecycle diagram](lifecycle.png) +![Lifecycle diagram](../../../../assets/lifecycle.png) ### Raw Specifications All new specifications are **raw** specifications. Changes to raw specifications can be unilateral and arbitrary. Those seeking to implement a raw specification should ask for it to be made a draft specification. Raw specifications have no contractual weight.