docs: Docs buffer overrun improvement

[erikmagkekse]

Description

Just a small documentation improvement with example code how traffic shaping could be done on a OS Level.
I troubleshooted that issue for many hours, found out about this helpful page but didn't found any examples. I think that will be helpful for many other users too.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ReenigneArcher]

@gschintgen could you review this as you originally added this section to the docs?

[ReenigneArcher]

I have a few suggestions below to improve the spacing and syntax highlighting.

[ReenigneArcher]

Suggested change

	Such a solution on Linux could look like that:
	```
	# 1) Remove existing qdisc (pfifo_fast)
	Such a solution on Linux could look like that:
	```bash
	# 1) Remove existing qdisc (pfifo_fast)

[ReenigneArcher]

Suggested change

	In that way only the Sunshine traffic is limited by 1 Gbit. This is not persistent on reboots.
	In that way only the Sunshine traffic is limited by 1 Gbit. This is not persistent on reboots.