Update instructions as per review suggestions

Author: praveenkuttappan

eng/common/instructions/azsdk-tools/typespec-to-sdk.instructions.md

@@ -22,8 +22,8 @@ As a first step, you must prompt the user to understand the intention of SDK gen
 
 Generate SDK locally in cases below:
 - If the user wants to walk through each SDK generation step locally. This approach requires user to have the setup for each language to generate SDK locally. User can create a pull request for each language after completing all the steps in SDK generation successfully to get the generated SDK reviewed and merged.
-- If the user wants to troubleshoot a failed SDK generation by the pipeline.
 - If SDK or client.tsp customizations are needed before creating a pull request.
+- If the user wants to add tests, samples or any customization to the generated SDK.
 
 Generate SDK using pipeline:
 - If the user wants to generate SDK and get a PR automatically created in Azure SDK language repositories. This approach can be followed if the user does not want to setup local environment for each language.
@@ -53,7 +53,8 @@ Follow the steps in #file:local-sdk-workflow.instructions.md to generate and bui
 2. Monitor pipeline status after 15 minutes and provide updates. If pipeline is in progress, inform user that it may take additional time and check the status later.
 3. Display generated SDK PR links when available. If pipeline fails, inform user with error details and suggest to check pipeline logs for more information.
 4. If SDK pull request is available for all languages, ask user to review generated SDK pull request and mark them as ready for review when they are ready to get them reviewed and merged.
-5. If SDK pull request was created for test purposes, inform user to close the test SDK pull request.
+5. Inform the user that they can checkout generated SDK pull request locally and add more tests, samples or code customizations if needed using local SDK generation tools.
+6. If SDK pull request was created for test purposes, inform user to close the test SDK pull request.
 **Success Criteria**: SDK generation pipeline initiated and SDKs generated
 
 ## Step: SDK release plan