I'm editing my first dhcp file and I googled the world to figure out how to view the errors <journalctl -xe> and received errors called out like the following:

/etc/dhcp/dhcpd.conf line 991: expecting left brace.
host B19-07-Alpha WB-6

I can find this host name in the file, but can't determine where the brace should exist, here is the host details in the file:

}
host B19-07-Alpha WB-6 {
hardware ethernet 00:23:8A:F8:61:00;
fixed-address 10.33.20.130;
# option host-name "D07-31-Alpha";
}

This type of "bracing" error is shown several times, need help figuring out what needs to be corrected, please.

For every right brace, you need to have a matching left brace.

I know this is just a clip of the file, but it shows to right braces, and only one left brace. I'm assuming that the first right brace does have a matching term above that you just haven't shown. Meanwhile, whatever is parsing this file, does feel that there is an error.

Also, many times it is very typical that the first instance where the syntax rules are violated can cause every following, but correct syntax, instance become an error. Therefore look at the very first problem line and go backwards in the file to verify that the syntax is correct.

I was really hoping not to have to provide the entire section, but I was unable to spot an "unmatched" bracket, perhaps you can
}

}
############################################################################

No I meant for you to search the file yourself.

Probably should not post that level of detail in the future, or edit/erase what you've posted if it is identifiable for your system/setup.

I copied that all, put it in an editor and globally searched/replaced { with [ --> 34 occurrences. Globally searched/replace } with ] --> 34 occurrences.

I don't know if that's the entire file, please don't post it. Meanwhile, the "syntax" may be wrong. Just because you have the same amount of { as you do } doesn't mean that one is not in the correct place. What if that group term needs to be terminated right up top and not at the end of the section/file. I don't know the syntax, but as said before, the first line number of the complaint is a good place to search.

Meanwhile, did you once have a working file? Check a file that does work, if possible.

Another approach is to try building the file in small sections and check each one as you you add them.
Error should be pretty obvious then...