edit to include iOS as well as Android

Author: genwhittTTD

docs/getting-started/gs-faqs.md

@@ -77,7 +77,7 @@ Here are some frequently asked questions for publishers using the UID2 framework
 - [What is the uniqueness and rotation policy for UID2 tokens?](#what-is-the-uniqueness-and-rotation-policy-for-uid2-tokens)
 - [What does a UID2 token look like in the bidstream?](#what-does-a-uid2-token-look-like-in-the-bidstream)
 - [Can I integrate UID2 with Single Sign-On (SSO)?](#can-i-integrate-uid2-with-single-sign-on-sso)
-- [I'm using Prebid with the Android SDK—what atype value should I use?](#im-using-prebid-with-the-android-sdkwhat-atype-value-should-i-use)
+- [I'm using Prebid with a Mobile SDK—what atype value should I use?](#im-using-prebid-with-a-mobile-sdkwhat-atype-value-should-i-use)
 
 #### How can I test that the DII sent and the returned token match up?
 
@@ -164,11 +164,11 @@ Yes. With popular <a href="../ref-info/glossary-uid#gl-sso">SSO</a> integration
 
 For details, see [Publisher Integration with SSO Providers](/docs/ref-info/ref-integration-sso-providers.md).
 
-#### I'm using Prebid with the Android SDK&#8212;what atype value should I use?
+#### I'm using Prebid with a Mobile SDK&#8212;what atype value should I use?
 
 According to the IAB documentation, the `atype` (agent type) value indicates the type of user agent that the match is from. IAB recommends defining this property.
 
-If you're using Prebid with the Android SDK, use an `atype` value of `3`, indicating a person-based ID.
+If you're using Prebid with the [SDK for Android](../sdks/sdk-ref-android.md) or the [SDK for iOS](../sdks/sdk-ref-ios.md), use an `atype` value of `3`, indicating a person-based ID.
 
 For details, refer to these sections in the IAB documentation:
 - [Object: Extended Identifier UIDs](https://github.com/InteractiveAdvertisingBureau/AdCOM/blob/main/AdCOM%20v1.0%20FINAL.md#object_eid_uids)