docs: fix broken App Transport Security links and update ATS documentation

docs/images.md

@@ -114,7 +114,7 @@ These approaches provide no safety checks. It's up to you to guarantee that thos
 
 ## Network Images
 
-Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](publishing-to-app-store.md#1-enable-app-transport-security) requirements on iOS.
+Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](https://developer.apple.com/documentation/security/preventing_insecure_network_connections) requirements on iOS.
 
 ```tsx
 // GOOD

docs/network.md

@@ -188,7 +188,7 @@ export default App;
 </Tabs>
 
 :::info
-By default, iOS 9.0 or later enforce App Transport Security (ATS). ATS requires any HTTP connection to use HTTPS. If you need to fetch from a cleartext URL (one that begins with `http`) you will first need to [add an ATS exception](integration-with-existing-apps.md#test-your-integration). If you know ahead of time what domains you will need access to, it is more secure to add exceptions only for those domains; if the domains are not known until runtime you can [disable ATS completely](publishing-to-app-store.md#1-enable-app-transport-security). Note however that from January 2017, [Apple's App Store review will require reasonable justification for disabling ATS](https://forums.developer.apple.com/thread/48979). See [Apple's documentation](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW33) for more information.
+By default, iOS enforces App Transport Security (ATS), requiring any HTTP connection to use HTTPS. If you need to fetch from a cleartext URL (one that begins with `http`), you must configure an ATS exception in your `Info.plist` file using [`NSAppTransportSecurity`](https://developer.apple.com/documentation/bundleresources/information_property_list/nsapptransportsecurity). It is recommended to add exceptions only for specific domains using `NSExceptionDomains` rather than disabling ATS globally (`NSAllowsArbitraryLoads`), as Apple's App Store review requires justification for disabling ATS. See Apple's documentation on [Preventing Insecure Network Connections](https://developer.apple.com/documentation/security/preventing_insecure_network_connections) for more information.
 :::
 
 :::tip

website/versioned_docs/version-0.77/images.md

@@ -99,7 +99,7 @@ These approaches provide no safety checks. It's up to you to guarantee that thos
 
 ## Network Images
 
-Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](publishing-to-app-store.md#1-enable-app-transport-security) requirements on iOS.
+Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](https://developer.apple.com/documentation/security/preventing_insecure_network_connections) requirements on iOS.
 
 ```tsx
 // GOOD

website/versioned_docs/version-0.77/network.md

@@ -181,7 +181,7 @@ export default App;
 </TabItem>
 </Tabs>
 
-> By default, iOS 9.0 or later enforce App Transport Security (ATS). ATS requires any HTTP connection to use HTTPS. If you need to fetch from a cleartext URL (one that begins with `http`) you will first need to [add an ATS exception](integration-with-existing-apps.md#test-your-integration). If you know ahead of time what domains you will need access to, it is more secure to add exceptions only for those domains; if the domains are not known until runtime you can [disable ATS completely](publishing-to-app-store.md#1-enable-app-transport-security). Note however that from January 2017, [Apple's App Store review will require reasonable justification for disabling ATS](https://forums.developer.apple.com/thread/48979). See [Apple's documentation](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW33) for more information.
+> By default, iOS enforces App Transport Security (ATS), requiring any HTTP connection to use HTTPS. If you need to fetch from a cleartext URL (one that begins with `http`), you must configure an ATS exception in your `Info.plist` file using [`NSAppTransportSecurity`](https://developer.apple.com/documentation/bundleresources/information_property_list/nsapptransportsecurity). It is recommended to add exceptions only for specific domains using `NSExceptionDomains` rather than disabling ATS globally (`NSAllowsArbitraryLoads`), as Apple's App Store review requires justification for disabling ATS. See Apple's documentation on [Preventing Insecure Network Connections](https://developer.apple.com/documentation/security/preventing_insecure_network_connections) for more information.
 
 > On Android, as of API Level 28, clear text traffic is also blocked by default. This behaviour can be overridden by setting [`android:usesCleartextTraffic`](https://developer.android.com/guide/topics/manifest/application-element#usesCleartextTraffic) in the app manifest file.
 

website/versioned_docs/version-0.78/images.md

@@ -99,7 +99,7 @@ These approaches provide no safety checks. It's up to you to guarantee that thos
 
 ## Network Images
 
-Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](publishing-to-app-store.md#1-enable-app-transport-security) requirements on iOS.
+Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](https://developer.apple.com/documentation/security/preventing_insecure_network_connections) requirements on iOS.
 
 ```tsx
 // GOOD

website/versioned_docs/version-0.78/network.md

@@ -181,7 +181,7 @@ export default App;
 </TabItem>
 </Tabs>
 
-> By default, iOS 9.0 or later enforce App Transport Security (ATS). ATS requires any HTTP connection to use HTTPS. If you need to fetch from a cleartext URL (one that begins with `http`) you will first need to [add an ATS exception](integration-with-existing-apps.md#test-your-integration). If you know ahead of time what domains you will need access to, it is more secure to add exceptions only for those domains; if the domains are not known until runtime you can [disable ATS completely](publishing-to-app-store.md#1-enable-app-transport-security). Note however that from January 2017, [Apple's App Store review will require reasonable justification for disabling ATS](https://forums.developer.apple.com/thread/48979). See [Apple's documentation](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW33) for more information.
+> By default, iOS enforces App Transport Security (ATS), requiring any HTTP connection to use HTTPS. If you need to fetch from a cleartext URL (one that begins with `http`), you must configure an ATS exception in your `Info.plist` file using [`NSAppTransportSecurity`](https://developer.apple.com/documentation/bundleresources/information_property_list/nsapptransportsecurity). It is recommended to add exceptions only for specific domains using `NSExceptionDomains` rather than disabling ATS globally (`NSAllowsArbitraryLoads`), as Apple's App Store review requires justification for disabling ATS. See Apple's documentation on [Preventing Insecure Network Connections](https://developer.apple.com/documentation/security/preventing_insecure_network_connections) for more information.
 
 > On Android, as of API Level 28, clear text traffic is also blocked by default. This behaviour can be overridden by setting [`android:usesCleartextTraffic`](https://developer.android.com/guide/topics/manifest/application-element#usesCleartextTraffic) in the app manifest file.
 

website/versioned_docs/version-0.79/images.md

@@ -99,7 +99,7 @@ These approaches provide no safety checks. It's up to you to guarantee that thos
 
 ## Network Images
 
-Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](publishing-to-app-store.md#1-enable-app-transport-security) requirements on iOS.
+Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](https://developer.apple.com/documentation/security/preventing_insecure_network_connections) requirements on iOS.
 
 ```tsx
 // GOOD

website/versioned_docs/version-0.79/network.md

@@ -181,7 +181,7 @@ export default App;
 </TabItem>
 </Tabs>
 
-> By default, iOS 9.0 or later enforce App Transport Security (ATS). ATS requires any HTTP connection to use HTTPS. If you need to fetch from a cleartext URL (one that begins with `http`) you will first need to [add an ATS exception](integration-with-existing-apps.md#test-your-integration). If you know ahead of time what domains you will need access to, it is more secure to add exceptions only for those domains; if the domains are not known until runtime you can [disable ATS completely](publishing-to-app-store.md#1-enable-app-transport-security). Note however that from January 2017, [Apple's App Store review will require reasonable justification for disabling ATS](https://forums.developer.apple.com/thread/48979). See [Apple's documentation](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW33) for more information.
+> By default, iOS enforces App Transport Security (ATS), requiring any HTTP connection to use HTTPS. If you need to fetch from a cleartext URL (one that begins with `http`), you must configure an ATS exception in your `Info.plist` file using [`NSAppTransportSecurity`](https://developer.apple.com/documentation/bundleresources/information_property_list/nsapptransportsecurity). It is recommended to add exceptions only for specific domains using `NSExceptionDomains` rather than disabling ATS globally (`NSAllowsArbitraryLoads`), as Apple's App Store review requires justification for disabling ATS. See Apple's documentation on [Preventing Insecure Network Connections](https://developer.apple.com/documentation/security/preventing_insecure_network_connections) for more information.
 
 > On Android, as of API Level 28, clear text traffic is also blocked by default. This behaviour can be overridden by setting [`android:usesCleartextTraffic`](https://developer.android.com/guide/topics/manifest/application-element#usesCleartextTraffic) in the app manifest file.
 

website/versioned_docs/version-0.80/images.md

@@ -99,7 +99,7 @@ These approaches provide no safety checks. It's up to you to guarantee that thos
 
 ## Network Images
 
-Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](publishing-to-app-store.md#1-enable-app-transport-security) requirements on iOS.
+Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](https://developer.apple.com/documentation/security/preventing_insecure_network_connections) requirements on iOS.
 
 ```tsx
 // GOOD

website/versioned_docs/version-0.80/network.md

@@ -181,7 +181,7 @@ export default App;
 </TabItem>
 </Tabs>
 
-> By default, iOS 9.0 or later enforce App Transport Security (ATS). ATS requires any HTTP connection to use HTTPS. If you need to fetch from a cleartext URL (one that begins with `http`) you will first need to [add an ATS exception](integration-with-existing-apps.md#test-your-integration). If you know ahead of time what domains you will need access to, it is more secure to add exceptions only for those domains; if the domains are not known until runtime you can [disable ATS completely](publishing-to-app-store.md#1-enable-app-transport-security). Note however that from January 2017, [Apple's App Store review will require reasonable justification for disabling ATS](https://forums.developer.apple.com/thread/48979). See [Apple's documentation](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW33) for more information.
+> By default, iOS enforces App Transport Security (ATS), requiring any HTTP connection to use HTTPS. If you need to fetch from a cleartext URL (one that begins with `http`), you must configure an ATS exception in your `Info.plist` file using [`NSAppTransportSecurity`](https://developer.apple.com/documentation/bundleresources/information_property_list/nsapptransportsecurity). It is recommended to add exceptions only for specific domains using `NSExceptionDomains` rather than disabling ATS globally (`NSAllowsArbitraryLoads`), as Apple's App Store review requires justification for disabling ATS. See Apple's documentation on [Preventing Insecure Network Connections](https://developer.apple.com/documentation/security/preventing_insecure_network_connections) for more information.
 
 > On Android, as of API Level 28, clear text traffic is also blocked by default. This behaviour can be overridden by setting [`android:usesCleartextTraffic`](https://developer.android.com/guide/topics/manifest/application-element#usesCleartextTraffic) in the app manifest file.
 

website/versioned_docs/version-0.81/images.md

@@ -99,7 +99,7 @@ These approaches provide no safety checks. It's up to you to guarantee that thos
 
 ## Network Images
 
-Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](publishing-to-app-store.md#1-enable-app-transport-security) requirements on iOS.
+Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](https://developer.apple.com/documentation/security/preventing_insecure_network_connections) requirements on iOS.
 
 ```tsx
 // GOOD

website/versioned_docs/version-0.81/network.md

@@ -182,7 +182,7 @@ export default App;
 </Tabs>
 
 :::info
-By default, iOS 9.0 or later enforce App Transport Security (ATS). ATS requires any HTTP connection to use HTTPS. If you need to fetch from a cleartext URL (one that begins with `http`) you will first need to [add an ATS exception](integration-with-existing-apps.md#test-your-integration). If you know ahead of time what domains you will need access to, it is more secure to add exceptions only for those domains; if the domains are not known until runtime you can [disable ATS completely](publishing-to-app-store.md#1-enable-app-transport-security). Note however that from January 2017, [Apple's App Store review will require reasonable justification for disabling ATS](https://forums.developer.apple.com/thread/48979). See [Apple's documentation](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CocoaKeys.html#//apple_ref/doc/uid/TP40009251-SW33) for more information.
+By default, iOS enforces App Transport Security (ATS), requiring any HTTP connection to use HTTPS. If you need to fetch from a cleartext URL (one that begins with `http`), you must configure an ATS exception in your `Info.plist` file using [`NSAppTransportSecurity`](https://developer.apple.com/documentation/bundleresources/information_property_list/nsapptransportsecurity). It is recommended to add exceptions only for specific domains using `NSExceptionDomains` rather than disabling ATS globally (`NSAllowsArbitraryLoads`), as Apple's App Store review requires justification for disabling ATS. See Apple's documentation on [Preventing Insecure Network Connections](https://developer.apple.com/documentation/security/preventing_insecure_network_connections) for more information.
 :::
 
 :::tip

website/versioned_docs/version-0.82/images.md

@@ -99,7 +99,7 @@ These approaches provide no safety checks. It's up to you to guarantee that thos
 
 ## Network Images
 
-Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](publishing-to-app-store.md#1-enable-app-transport-security) requirements on iOS.
+Many of the images you will display in your app will not be available at compile time, or you will want to load some dynamically to keep the binary size down. Unlike with static resources, _you will need to manually specify the dimensions of your image_. It's highly recommended that you use https as well in order to satisfy [App Transport Security](https://developer.apple.com/documentation/security/preventing_insecure_network_connections) requirements on iOS.
 
 ```tsx
 // GOOD