There is nowt in plain text. There is a bash script which is indecipherable unless you are an aforementioned guru, and which is completely useless on Windows. There is no info on what should go under [Interfaces], no mention that there' s even a [Peer] never mind what might go under that. Plenty of long-winded command line stuff that's inappropriate.
There are three ways to use wireguard:
(1) Lots of small wg commands (aka pure wireguard). This is aimed at a nitty gritty network/linux admin audience that writes their own routing rules and creates their own bridge interfaces. This is what the developers of wireguard think and breathe. Almost all new users will want to run 100 miles from this and it's not made clear that this really isn't a good starting point.
(2) a wg-quick config file (what most people use, simpler).
The windows wireguard GUI expects this. Understanding and creating these files (on both ends of the connection) is still quite complicated and requires a good chunk of networking knowledge, but once they're made they are super-easy to use. There are guides on the web on how to make these.
(3) a paid service that hosts part of the network for you and provides the wg-quick config files, so you just have to throw them at your copy of wireguard and it just works. Note: it's
possible to do this in a way where your traffic can't be decrypted by them, even though it transits through them, but not if they're providing you the wg-quick files (which means they have all your private keys).
It sounds like you stumbled upon (1). Yes this causes lots of confusion for new users, but it's still better than OpenVPN

If you are knowledgeable enough to know what a static IP and portforwarding is then (2) is an option, otherwise (3) might be more attractive for you.