Build Fix

Author: MicrosoftGuyJFlo

articles/active-directory/conditional-access/location-condition.md

@@ -120,7 +120,7 @@ This option applies to:
 
 #### Multifactor authentication trusted IPs
 
-Using the trusted ips section of multifactor authentication's service settings is no longer recommended. This control only accepts IPv4 addresses and should only be used for specific scenarios covered in the article [Configure Azure AD Multi-Factor Authentication settings](../authentication/howto-mfa-mfasettings.md#trusted-ips)
+Using the trusted IPs section of multifactor authentication's service settings is no longer recommended. This control only accepts IPv4 addresses and should only be used for specific scenarios covered in the article [Configure Azure AD Multi-Factor Authentication settings](../authentication/howto-mfa-mfasettings.md#trusted-ips)
 
 If you have these trusted IPs configured, they show up as **MFA Trusted IPs** in the list of locations for the location condition.
 
@@ -138,6 +138,8 @@ You can discover IPv6 traffic in your tenant by going the [Azure AD sign-in acti
 
 You can also find the client IP by clicking a row in the report, and then going to the “Location” tab in the sign-in activity details. 
 
+:::image type="content" source="media/location-condition/sign-in-logs-showing-ip-address-filter-for-ipv6.png" alt-text="A screenshot showing Azure AD Sign-in logs and an IP address filter for IPv6 addresses." lightbox="media/location-condition/sign-in-logs-showing-ip-address-filter-for-ipv6.png":::
+
 ## What you should know
 
 ### When is a location evaluated?