Update documentation for deprecated inputs

Author: caendesilva

README.md

@@ -74,9 +74,7 @@ There are a few more configuration options available, that can be supplied to th
 | `framework-version`    | Specify the HydePHP Framework version to use<br><small>(only applicable for [anonymous projects](https://hydephp.github.io/action/#anonymous-projects))</small> | "latest"      |
 | `directory`            | The directory to use as the project root                                                                                                                        | none          |
 | `config`               | String of lines to add to the `hyde.yml` config file                                                                                                            | none          |
-| `env-site-name`        | Set the `SITE_NAME` environment variable                                                                                                                        | _none_        |
-| `env-site-url`         | Set the `SITE_URL` environment variable                                                                                                                         | _none_        |
-| `env-torchlight-token` | Set the `TORCHLIGHT_TOKEN` environment variable                                                                                                                 | _none_        |
+| `env`                  | List of environment variables to set in the format `NAME=value`                                                                                                 | _none_        |
 
 ## Further documentation
 

docs/index.md

@@ -217,6 +217,24 @@ See the [HydePHP documentation](https://hydephp.com/docs/1.x/customization#yaml-
 
 >warning If your inputs contain sensitive information, you should use [GitHub Secrets](https://docs.github.com/en/actions/reference/encrypted-secrets) to store them.
 
+#### `env`
+
+You can set arbitrary environment variables using the `env` input. Simply provide each variable in KEY=VALUE format, one per line:
+
+```yaml
+- uses: hydephp/action@master
+  with:
+    deploy-to: "pages"
+    env: |
+      SITE_NAME=My Site
+      SITE_URL=https://example.com
+      TORCHLIGHT_TOKEN=${{ secrets.TORCHLIGHT_TOKEN }}
+```
+
+The environment variables will be available during the build process. Note that if you're using sensitive information, you should use GitHub Secrets instead of hardcoding the values. Also make sure your input is valid "dotenv" syntax.
+
+### Deprecated inputs
+
 You can also pass set the following inputs to be passed as environment variables for the build process:
 
 #### `env-site-name`
@@ -236,19 +254,3 @@ Sets the `SITE_URL` environment variable
 > Deprecated: Use the `env` input instead with `TORCHLIGHT_TOKEN=value`
 
 Sets the `TORCHLIGHT_TOKEN` environment variable
-
-#### `env`
-
-You can set arbitrary environment variables using the `env` input. Simply provide each variable in KEY=VALUE format, one per line:
-
-```yaml
-- uses: hydephp/action@master
-  with:
-    deploy-to: "pages"
-    env: |
-      SITE_NAME=My Site
-      SITE_URL=https://example.com
-      TORCHLIGHT_TOKEN=${{ secrets.TORCHLIGHT_TOKEN }}
-```
-
-The environment variables will be available during the build process. Note that if you're using sensitive information, you should use GitHub Secrets instead of hardcoding the values. Also make sure your input is valid "dotenv" syntax.