tazlin
commented
3 weeks ago I don’t follow what it is you’re trying to fix with the wording change. A standard part of the update process right now is to run git pull, so the template is updated to the latest version, and if it’s missing, will be re-added to the local clone. The template file therefore will reappear anyway after the first update.
While I can sort of see where you are coming from, I think the wording change actually would end up being more confusing in the long run due to the dynamics I mentioned above.
The issue should hopefully become moot in time as the intention has always been to have a (web) GUI config creator that handles this for the user.
"make a copy of" is confusing: I get the intended purpose of the user making such a copy, but then the question comes up if keeping the original document will break the code in any way; renaming the file removes that concern. If the file breaks in any way where the original is needed, downloading the file again from the repo could be utilized