fix: PSA language emphasizing not for production (#2322)

Author: dchoi27

packages/website/pages/docs/how-to/pinning-service.md

@@ -2,7 +2,7 @@
 
 You can ask NFT.Storage to archive data that is already on the [IPFS](https://ipfs.io) distributed storage network with this API. This data will remain perpetually available over IPFS (backed by [Filecoin decentralized storage](https://nft.storage/docs/concepts/decentralized-storage/#filecoin-for-verifiable-content-persistence)).
 
-NFT.Storage provides a pinning service that is modeled closely on the [IPFS Pinning Service API specification](https://ipfs.github.io/pinning-services-api-spec/).
+NFT.Storage provides a pinning service that is modeled closely on the [IPFS Pinning Service API specification](https://ipfs.github.io/pinning-services-api-spec/). **NFT.Storage's Pinning Service API is not to be used for ongoing production traffic, but rather for one-time migrations.**
 
 **You do not need to request access if you are storing data with NFT.Storage directly. Data stored with NFT.Storage is persisted indefinitely by default. This API is only useful if you are looking to store data with NFT.Storage that is already available on the IPFS network. Even in these situations, if you are able to, we recommend you generate a CAR file from a IPFS node hosting the content and directly upload that to NFT.Storage (e.g., run `ipfs dag export` from your local node) rather than use the Pinning API.**