broken links

Author: mcevoy-building7

articles/healthcare-apis/dicom/dicom-register-application.md

@@ -77,7 +77,7 @@ The following steps are required for the DICOM service. In addition, user access
 
 3. Select scopes (permissions) that the confidential client application will ask for on behalf of a user. Select **Dicom.ReadWrite**, and then select **Add permissions**.
 
-   [ ![Select permissions scopes.](./media/dicom-select-scopes-new.png) ](./media/dicom-select-scopes.new.png#lightbox)
+   [Select permissions scopes](./media/dicom-select-scopes-new.png) ](./media/dicom-select-scopes.new.png#lightbox)
 
 Your application registration is now complete.
 

articles/healthcare-apis/register-application.md

@@ -77,7 +77,7 @@ The following steps are required for the DICOM service, but optional for the FHI
 
    If you're using Azure Health Data Services, you'll add a permission to the DICOM service by searching for **Azure API for DICOM** under **APIs my organization** uses. 
 
-   [ ![Search API permissions](dicom/media/dicom-search-apis-permissions.png) ](dicom/media/dicom-search-apis-permissions.png#lightbox)
+   [ ![Search API permissions](dicom/media/dicom-search-api-permissions.png) ](dicom/media/dicom-search-api-permissions.png#lightbox)
 
    The search result for Azure API for DICOM will only return if you've already deployed the DICOM service in the workspace.