Update markdown

Thanks for pointing to that commit — it definitely shows how the Docker setup has evolved in that tutorial and why certain changes were made to the build context.

From experience watching similar repos, keeping the Dockerfile and related configs clean and minimal makes it much easier to debug build issues, especially on CI/CD runners. One thing I always recommend is checking for unnecessary file copies (COPY . .) that pull in large files or config folders — that often bloats images and can cause unexpected behavior.

Also worth noting: when linking to external guides or examples from production content, I usually prefer plain hyperlinks rather than embeds, to avoid extra scripts slowing down page loads. That’s something I pay attention to on my own sites too, like Bus Simulator Indonesia and Bus Simulator Ultimate, where performance matters for visitors.