Avoids losing the custom change in #13 until the table name for
the security section can be customized.
The problem with this is going to be you have to remember to build
the updated docs locally when the yaml file is updated; that's going
to get in the way of building against the main project's yaml file, so
this needs to be a temporary workaround to support #13.
Avoids losing the custom change in #13 until the table name for the security section can be customized.
The problem with this is going to be you have to remember to build the updated docs locally when the yaml file is updated; that's going to get in the way of building against the main project's yaml file, so this needs to be a temporary workaround to support #13.