just use demo3.gif

README.md

@@ -8,7 +8,9 @@ A simple terminal UI for docker and docker-compose, written in Go with the [gocu
 
 
 
-![Gif](/docs/resources/demo.gif)
+![Gif](/docs/resources/demo3.gif)
+
+[Demo](https://youtu.be/NICqQPxwJWw)
 
 Minor rant incoming: Something's not working? Maybe a service is down. `docker-compose ps`. Yep, it's that microservice that's still buggy. No issue, I'll just restart it: `docker-compose restart`. Okay now let's try again. Oh wait the issue is still there. Hmm. `docker-compose ps`. Right so the service must have just stopped immediately after starting. I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services. I could get the logs for just that one service with `docker compose logs --follow myservice` but that dies everytime the service dies so I'd need to run that command every time I restart the service. I could alternatively run `docker-compose up myservice` and in that terminal window if the service is down I could just `up` it again, but now I've got one service hogging a terminal window even after I no longer care about its logs. I guess when I want to reclaim the terminal realestate I can do `ctrl+P,Q`, but... wait, that's not working for some reason. Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service.
 
@@ -82,7 +84,7 @@ For contributor discussion about things not better discussed here in the repo, j
 
 If you would like to support the development of lazydocker, please donate
 
-[![Donate](https://d1iczxrky3cnb2.cloudfront.net/button-medium-blue.png)](https://donorbox.org/https://donorbox.org/lazydocker)
+[![Donate](https://d1iczxrky3cnb2.cloudfront.net/button-medium-blue.png)](https://donorbox.org/lazydocker)
 
 ## Social