Apply suggestions from code review

Author: ttorble

articles/healthcare-apis/azure-api-for-fhir/use-smart-on-fhir-proxy.md

@@ -10,7 +10,7 @@ author: expekesheth
 ms.date: 06/03/2022
 ---
 
-# SMART on FHIR Overview
+# SMART on FHIR overview
 
 [SMART on FHIR](https://docs.smarthealthit.org/) is a set of open specifications to integrate partner applications with FHIR servers and electronic medical records systems that have Fast Healthcare Interoperability Resources (FHIR®) interfaces. One of the main purposes of the specifications is to describe how an application should discover authentication endpoints for an FHIR server and start an authentication sequence. 
 

articles/healthcare-apis/fhir/smart-on-fhir.md

@@ -10,7 +10,7 @@ author: expekesheth
 ms.date: 11/10/2022
 ---
 
-# SMART on FHIR: 
+# SMART on FHIR
 
 [SMART on FHIR](https://docs.smarthealthit.org/) is a set of open specifications to integrate partner applications with FHIR servers and electronic medical records systems that have Fast Healthcare Interoperability Resources (FHIR®) interfaces. One of the main purposes of the specifications is to describe how an application should discover authentication endpoints for an FHIR server and start an authentication sequence. 
 
@@ -125,7 +125,7 @@ dotnet run
 
 After you start the SMART on FHIR app launcher, you can point your browser to `https://localhost:5001`, where you should see the following screen:
 
-![SMART on FHIR app launcher](media/smart-on-fhir/smart-on-fhir-app-launcher.png)
+![Screenshot showing SMART on FHIR app launcher.](media/smart-on-fhir/smart-on-fhir-app-launcher.png)
 
 When you enter **Patient**, **Encounter**, or **Practitioner** information, you'll notice that the **Launch context** is updated. When you're using the FHIR service, the launch context is simply a JSON document that contains information about patient, practitioner, and more. This launch context is base64 encoded and passed to the SMART on FHIR app as the `launch` query parameter. According to the SMART on FHIR specification, this variable is opaque to the SMART on FHIR app and passed on to the identity provider. 
 
@@ -141,7 +141,7 @@ These fields are meant to provide guidance to the app, but they don't convey any
 
 Notice that the SMART on FHIR app launcher updates the **Launch URL** information at the bottom of the page. Select **Launch** to start the sample app, and you should see something like this sample:
 
-![SMART on FHIR app](media/smart-on-fhir/smart-on-fhir-app.png)
+![Screenshot showing SMART on FHIR app.](media/smart-on-fhir/smart-on-fhir-app.png)
 
 Inspect the token response to see how the launch context fields are passed on to the app.