docs: move custom store name prefix from readme to contributing guide

Author: Orkuncakilkaya

README.md

@@ -78,18 +78,6 @@ By default, the service package provided in releases assumes the following names
 * `Fingerprint_Compute_Config_Store_<SERVICE_ID>`
 * `Fingerprint_Compute_Secret_Store_<SERVICE_ID>`
 
-To use a custom name prefix for both stores, use the `STORE_NAME_PREFIX` environment variable to build a custom service package:
-
-```shell=
-STORE_NAME_PREFIX=CustomName fastly compute build
-```
-
-Your custom built package in `pkg/fingerprint-fastly-compute-proxy-integration.tar.gz` will use your custom prefix in store names like:
-
-* `CustomName_Config_Store_<SERVICE_ID>`
-* `CustomName_Secret_Store_<SERVICE_ID>`
-
-
 ## Feedback and support
 
 Please reach out to our [Customer Success team](https://fingerprint.com/support/) if run into any issues with the integration.

contributing.md

@@ -22,6 +22,20 @@ For proposing changes, use the standard [pull request approach](https://docs.git
 2. Run `pnpm build` to compile the project and assemble the WebAssembly output.
 3. The build artifact is located in the `bin/main.wasm` file, which will be deployed to Fastly.
 
+### Custom Store Name Prefix
+
+To use a custom name prefix for both(Secret and Config) stores, use the `STORE_NAME_PREFIX` environment variable to build a custom service package:
+
+```shell=
+STORE_NAME_PREFIX=CustomName fastly compute build
+```
+
+Your custom built package in `pkg/fingerprint-fastly-compute-proxy-integration.tar.gz` will use your custom prefix in store names like:
+
+* `CustomName_Config_Store_<SERVICE_ID>`
+* `CustomName_Secret_Store_<SERVICE_ID>`
+
+
 ### Code Style
 
 We enforce code quality using [ESLint](https://eslint.org/) and [Prettier](https://prettier.io/). To check code style: