Update deploy.md add hints on restrictions on availability of Environ…

…ments and how to find explicit values in the README

Further improvements This can be cross linked to the creation of the repo, where I suggested a similar hint.

docs/plone-deployment/deploy.md

@@ -102,12 +102,19 @@ Monitor the logs of each service with these commands:
 
 #### Creating a New Environment
 
+````{important}
+When you cannot see the Environment option on the left in the Settings of your Github repo, you may have a private repo in a free account. You either need to use a public repo in a free account or upgrade to at least Github Pro. If you use a free additional organisation under control of a payed accout, the Environment is also not visible in the above situation.
+````
+
 1. Log in to [GitHub](https://github.com/).
 2. Navigate to the project repository.
 3. Click `Settings`.
 4. Select `Environments`, then `New environment`.
-5. Name it after your public URL and configure the environment.
+5. Name it after the public URL of the deployment server and configure the environment.
 
+````{important}
+**Tip:** You find exlicit instructions which values to fill into these fields for your particular project in the provided `devops/README-GHA.md` file
+````
 #### Adding Environment Secrets
 
 Add secrets in the `Secrets` section of your environment. Refer to the table below: