diff --git a/software-development/gitea/README.md b/software-development/gitea/README.md
index a534170..6893635 100644
--- a/software-development/gitea/README.md
+++ b/software-development/gitea/README.md
@@ -4,17 +4,25 @@ Followed instructions on Gitea page: https://docs.gitea.com/next/installation/in
 
 ### Steps
 1. Create a new user to own the gitea folder.
-`sudo groupadd gitea && sudo useradd giteauser && sudo usermod -a -G gitea giteauser && chown -r gitea:giteauser .`
+```
+sudo groupadd gitea && sudo useradd giteauser && sudo usermod -a -G gitea giteauser && chown -r gitea:giteauser .
+```
 2. Run via Docker Compose
-`docker-compose up -d`
+```
+
+docker-compose up -d
+```
 3. Test postgresql
-`docker exec -it gitea_db bash`
-`psql -h 127.0.0.1 -p 5432 -U olomana_readwrite -d gitea`
+```
+docker exec -it gitea_db bash
+psql -h 127.0.0.1 -p 5432 -U olomana_readwrite -d gitea
+```
+
 4. Go to xxx.xxx.xx.xxx:3000 and fill out initial config. Everything should match up to default value.
 Some things that were weird:
 - could not use any port that wasnt default postgresql (5432)
-- had to make sure to specify database container by the right name. Removed custom name and used just "databasei".
-Additionally, you must provision the first admin user in the initial config.
+- had to make sure to specify database container by the right name. Removed custom name and used just "database".
+Note that the first admin is set via env vars, by generating the password hash. Alternatively create your users by setting the env var that controls signups.
 5. Provision new users
 You can do that from the "Site Administration" view from the first admin user.
 6. Configure SSH
@@ -39,5 +47,10 @@ entryPoints:
 Settings > SSH/GPG Keys > Manage SSH Keys  
 Now should also be able to clone with SSH.
 
+### Running
+```
+docker compose down && docker compose build && docker compose up -d && docker logs -f gitea
+```
+
 ### References
 `https://docs.gitea.com/next/administration/config-cheat-sheet`