Missing configuration keywords, which are in Configuration documentation

[atlanteg]

Describe the bug
Missing configuration keywords, which are in Configuration documentation:
line 180: field source4 not found in type config.Peer
line 181: field source6 not found in type config.Peer
and
line 5: field next-hop-self-ebgp not found in type config.Config
line 6: field next-hop-self-ibgp not found in type config.Config

Environment

1. Output from pathvector version
   Pathvector 6.3.2
   Built c35220b on 2023-06-11T07:03:14Z
   No plugins
   BIRD: ready.
2. OS version
   DISTRIB_ID=Ubuntu
   DISTRIB_RELEASE=20.04
   DISTRIB_CODENAME=focal
   DISTRIB_DESCRIPTION="Ubuntu 20.04.6 LTS"
3. Minimum reproducible example of your Pathvector config file formatted with triple backticks with yaml language identifier

  core:
    local-pref: 50
    source4: 208.208.208.208
    source6: 2AAA:3AAA:1::A
    next-hop-self-ebgp: true
    next-hop-self-ibgp: true

And having these IP addresses set up on Linux's loopback interface: 208.208.208.208/32 , 2AAA:3AAA:1::A/128

To Reproduce
Steps to reproduce the behavior:

1. Copy this config to pathvector.yml...
2. Run pathvector -v generate
3. See error

Expected behavior
I would like to create some BGP sessions from source IP address of Loopback interface.
It seems that described Configuration parameters are supposed to be for this purpose. But not working in current release.
Why?

PS.
the same situation - not working keywords like:
next-hop-self-ibgp
next-hop-self-ebgp

[atlanteg]

1. I was able to put the keywords

asn: XXXX
router-id: 188.188.188.188
source4: 208.208.208.208
source6: 2AAA:3AAA:1::A

into the main config section in the beginning.
But my core ibgp sessions still don't use this loopback address as source to establish bgp session. They use local interface address.

2. But keywords:

next-hop-self-ebgp: true
next-hop-self-ibgp: true

are still not allowed neither in main config section nor in peer template or peer config.