fixing setParams doc

Author: madhavanmalolan

content/docs/js-sdk/generating-proof.mdx

@@ -164,19 +164,3 @@ Automatically trigger the optimal verification flow based on user's platform. Sh
 ```
 reclaimProofRequest.triggerReclaimFlow(options)
 ```
-
-## Passing variables through the proof object
-
-You can add custom key-value parameters to the proof request. These parameters will be included in the verified proof and can be used for application-specific metadata. However, the parameters are not cryptographically bound to the proof. If they are edited by a malicious user, there is no way to detect. So we recommend putting only metadata in parameters that are not strictly mission critical. This is useful to pass variables into the proof object instead of having to maintain state separately. For mission critical variables that should not be possible for the user to edit, please refer [`setContext`](preparing-request#set-context) instead.
-
-```
-reclaimProofRequest.setParams({
-  action: "account_verification",
-  timestamp: Date.now(),
-  ...
-});
-```
-
-
-
-

content/docs/js-sdk/preparing-request.mdx

@@ -17,7 +17,7 @@ This is the simplest version of creating a proof request.
 import { ReclaimProofRequest } from '@reclaimprotocol/js-sdk';
 ```
 
-## Create an endpoint to build the `Proof Request` on your backend
+## Setup a request on the backend
 ```javascript
 const reclaimProofRequest = await ReclaimProofRequest.init(
     'APP_ID',
@@ -84,6 +84,18 @@ reclaimProofRequest.setContext('address', 'message')
 - `address` : this is usually a unique identifier for the user. This could be an email address, a wallet address, or just a session id
 - `message` : this is an open field where you can add any other information that you want passed around from the build request to the callback endpoint. You can stringify jsons here for convenience. 
 
+## Set Parameters
+If you already know what the value of the extracted parameter is supposed to be, you can set that using `setParams`.
+For example, if you know that the user's name before hand - and you want them to prove something from a website and you need the name to match exactly, you should use set the name in the params.
+
+If the extracted parameter doesn't match the set parameter, the proof generation will fail.
+```
+reclaimProofRequest.setParams({ 
+    name : "John Doe"
+})
+```
+
+
 ## Set Callback 
 ```
 reclaimProofRequest.setAppCallbackUrl(url)

content/docs/js-sdk/verifying-proofs.mdx

@@ -4,7 +4,7 @@ description: Critical step to make sure user is not trying to defraud your app
 ---
 
 # Why do I need to verify, when the proof has already been generated?
-The [proof generation](/js-sdk/generating-proof) is a client side operation to protect the privacy and security of the user. However, if the user is malicious and you don't verify the proof on the backend, the user could use browser injections to trick your webapp to call `onSuccess` callback even without creating a valid proof. So, you must force your frontend to upload the proof generated or claimed to have been generated and verify them before you take the user to the next step in your business logic.
+The [proof generation](/js-sdk/generating-proof) is a client side operation. On Success Callback is only responsible for notifying when the proof is generated successfully. All the proofs generated should be verified on your backend as a malicious user can bypass any check you add on the frontend.
 
 Verifying proofs is a very simple light weight operation. You can think of it as verifying the digital signatures to make sure the data is tamper resistant.