From d5e0072498858c5d699ec091c41ae8961badcaee Mon Sep 17 00:00:00 2001
From: Afri Schoedon <179940409+schoedon@users.noreply.github.com>
Date: Wed, 9 Oct 2024 17:53:44 +0200
Subject: [PATCH] cosmetic: fix external links in 1/COSS (#100)

---
 vac/1/coss.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/vac/1/coss.md b/vac/1/coss.md
index 4af5d75..3f43e49 100644
--- a/vac/1/coss.md
+++ b/vac/1/coss.md
@@ -285,7 +285,7 @@ Contributors within the service SHOULD assist a *sub-domain* in creating a new s
 editing a specification, and
 promoting the status of a specification along with other tasks.
 Once a specification reaches some level of maturity by rough consensus,
-the specification SHOULD enter the [Vac RFC](rfc.vac.dev) process.
+the specification SHOULD enter the [Vac RFC](https://rfc.vac.dev/) process.
 Similar to the IETF working group adoption described in [RFC6174](https://www.rfc-editor.org/rfc/rfc6174.html),
 the Vac RFC process SHOULD facilitate all updates to the specification.
 
@@ -293,7 +293,7 @@ Specifications are introduced by projects,
 under a specific *domain*, with the intention of becoming technically mature documents.
 The IFT domain currently houses the following projects:
 
-- [Status](status.app)
+- [Status](https://status.app/)
 - [Waku](https://waku.org/)
 - [Codex](https://codex.storage/)
 - [Nimbus](https://nimbus.team/)