Dynamic objects (Address Objects) is missing

"...include SD-WAN..." should read "...including SD-WAN..."

"...complexity posses..." should read "...complexity poses..."

"...you should use the just the hostname..."
should read
"...you should use just the hostname..."

"A few object type, however, cannot be changed once they are created."
should read
"For a few object types, however, the name of the object cannot be changed after it is created."

I've appreciated this guide as it's helped me understand a bit more about Fortigates.

I'm wondering why you have chosen not to include a port number or port range for Single Service Objects.

I have an application that utilizes 6 ports. Given this naming convention, I believe they'd all be named the same: TCP-PCRES.

Can you also clarify why you use dashes for services objects instead of underscores?

As a newbie to Fortigate, I'd find it useful if all of the conventions listed would have examples. That way I'd be able to verify my understanding of the convention.

Cheers!

https://github.com/weis-victor/naming-conventions/blame/2935f320a5484c4754cc28250dbdeddb18d4d269/FOS-Naming-Conventions.md#L323

example is missing _sla