From bb67482afd4277f5b2e46d1f177af9b472be643d Mon Sep 17 00:00:00 2001
From: Taras Lazariv <taras.lazariv@tu-dresden.de>
Date: Mon, 7 Feb 2022 16:41:28 +0100
Subject: [PATCH] Priority for a fork

---
 doc.zih.tu-dresden.de/docs/contrib/contribute_container.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc.zih.tu-dresden.de/docs/contrib/contribute_container.md b/doc.zih.tu-dresden.de/docs/contrib/contribute_container.md
index 71cf44814..bf1aa2498 100644
--- a/doc.zih.tu-dresden.de/docs/contrib/contribute_container.md
+++ b/doc.zih.tu-dresden.de/docs/contrib/contribute_container.md
@@ -9,8 +9,9 @@ document might seem very long describing complex steps, contributing is quite ea
 
 Please follow this standard Git procedure for working with a local clone:
 
-1. Request access to the project or fork the project on
+1. Fork the project on
 [https://gitlab.hrz.tu-chemnitz.de/zih/hpcsupport/hpc-compendium](https://gitlab.hrz.tu-chemnitz.de/zih/hpcsupport/hpc-compendium)
+or request access to the project.
 1. Change to a local (unencrypted) filesystem. (We have seen problems running the container on an
 ecryptfs filesystem. So you might want to use e.g. `/tmp` as the start directory.)
 1. Create a new directory, e.g. with `mkdir hpc-wiki`
-- 
GitLab