Merge pull request #271776 from shellyhaverkamp/smh-powershell

Update PowerShell commands in Postman article

Author: v-dirichards

articles/healthcare-apis/fhir/azure-ad-b2c-setup.md

@@ -301,7 +301,7 @@ The validation process involves creating a patient resource in the FHIR service,
 
 Run the [Postman](https://www.postman.com) application locally or in a web browser. For steps to obtain the proper access to the FHIR service, see [Access the FHIR service using Postman](use-postman.md).
 
-When you follow the steps to [GET FHIR resource](use-postman.md#get-fhir-resource) section, the request returns an empty response because the FHIR service is new and doesn't have any patient resources.
+When you follow the steps to [GET FHIR resource](use-postman.md#get-the-fhir-resource) section, the request returns an empty response because the FHIR service is new and doesn't have any patient resources.
 
 #### Create a patient resource in the FHIR service
 

articles/healthcare-apis/fhir/media/postman/app-registration-permissions-2.png

@@ -98,7 +98,7 @@ Migrate applications that were pointing to the old FHIR server.
 
 - Reconfigure any remaining settings in the new Azure Health Data Services FHIR Service server after migration.
 
-- If you’d like to double check to make sure that the Azure Health Data Services FHIR Service and Azure API for FHIR servers have the same configurations, you can check both [metadata endpoints](use-postman.md#get-capability-statement) to compare and contrast the two servers.
+- If you’d like to double check to make sure that the Azure Health Data Services FHIR Service and Azure API for FHIR servers have the same configurations, you can check both [metadata endpoints](use-postman.md#get-the-capability-statement) to compare and contrast the two servers.
 
 - Set up any jobs that were previously running in your old Azure API for FHIR server (for example, \$export jobs)