The current documentation relates to the subdirectory for external configurations as /config. Read as UNIX path, the leading slash could be read as reference to the root directory /. Therefore I would suggest to use ./config to make it a little bit more understandable.
This is of course not a major issue, but IMHO makes it a little bit more understandable.
Comment From: wilkinsona
Thanks for spotting this, @obfischer, and raising a PR. I agree that /config is misleading. As a replacement, I wonder if config/ would be better than ./config. The trailing slash is commonly used to indicate that a path is a directory (and it's what both bash and zsh tab-complete to).
Comment From: snicoll
@obfischer any opinion about this? If you agree, we can also polish this as part of merging but we'd like to make sure the updated proposal addresses your concern.
Comment From: obfischer
I think @wilkinsona has a good point. I updated my pull request.
Comment From: snicoll
Thanks for the follow up and the contribution @obfischer