NGINX config and website path

Examples, where where e.g the design changed from say 1.24 to 1.25 and then again from 1.25 to 1.26. I seems (and I could be wrong here (and I can accept that)) there was a design change as to where the configs are set. As a learner - there seems more confusion.
It is ok to change design but allowance for design change impact examples may help.
This will allow folks like me to adapt to the change and have a path to upgrade.
I want to really communicate that this is not a run in with the dev team at all as I support opensource as much as I can. I understand that maybe there is a capacity problem or such (and when is it never the case).
I am stating that newbies may need more help than experienced folks, and docs (ref model) may help - especially like me you are on your own with noone to ask :wink:

A simple example:
In the docs it states as below - (however the doc does not tell you where the file is or it’s name. If you are experienced you already know but if yo not well … I am building everything from scratch and depend on the docs basically and I cannot follow.

Sample Configuration File with Multiple Contexts

The following configuration illustrates the use of contexts.

user nobody; # a directive in the 'main' context

events {
    # configuration of connection processing
}

http {
    # Configuration specific to HTTP and affecting all virtual servers

    server {
        # configuration of HTTP virtual server 1
        location /one {
2 Likes