[docs] Change configuration creation instructions (#2408)

* [docs] Change configuration creation instructions

This changes the wording to push people towards creating their own
configuration, without copying the whole example configuration. This
makes it much easier to reconcile necessary configruation changes on
upgrades.

* [docs] Reword container version section

This changes the wording in the Version section to make it more clear
what the risks of a moving tag are. It pushes people to use an explicit
release tag instead.

1 files changed, 2 insertions, 6 deletions

diff --git a/docs/getting_started/installation/metal.md b/docs/getting_started/installation/metal.md
index facc13326..6a4e50344 100644
--- a/docs/getting_started/installation/metal.md
+++ b/docs/getting_started/installation/metal.md
@@ -43,13 +43,9 @@ This will put the `gotosocial` binary in your current directory, in addition to
 
 ## Edit Configuration File
 
-Copy the configuration file from the example folder into your current directory:
+Create a new configuration file, based on the `config.yaml` from the `example` folder. You can copy the whole file, but make sure you only retain settings you've changed. This makes it easier to review configuration changes on release upgrades.
 
-```bash
-cp ./example/config.yaml .
-```
-
-Now open the file in your text editor of choice so that you can set some important configuration values. Change the following settings:
+You'll probably need to change the following settings:
 
 - Set `host` to whatever hostname you're going to be running the server on (eg., `example.org`).
 - Set `port` to `443`.