diff --git a/docs/appregistry.md b/docs/appregistry.md
index 4db609c8fbd..fc0b4157857 100644
--- a/docs/appregistry.md
+++ b/docs/appregistry.md
@@ -5,9 +5,7 @@ title: AppRegistry
Project with Native Code Required
-
- If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
-
+
If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
diff --git a/docs/debugging-native-code.md b/docs/debugging-native-code.md
index b44adedb0ee..a39cb908ef6 100644
--- a/docs/debugging-native-code.md
+++ b/docs/debugging-native-code.md
@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
## Accessing Logs
diff --git a/docs/linking.md b/docs/linking.md
index 9352e51ba2e..91912a5d856 100644
--- a/docs/linking.md
+++ b/docs/linking.md
@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
If you want to enable deep links in your app, please read the below guide:
diff --git a/docs/permissionsandroid.md b/docs/permissionsandroid.md
index 6387aa712fd..ec1f486ba37 100644
--- a/docs/permissionsandroid.md
+++ b/docs/permissionsandroid.md
@@ -5,9 +5,7 @@ title: PermissionsAndroid
Project with Native Code Required
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
diff --git a/docs/pushnotificationios.md b/docs/pushnotificationios.md
index 9ec9fcab911..5b3bedff114 100644
--- a/docs/pushnotificationios.md
+++ b/docs/pushnotificationios.md
@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
Handle notifications for your app, including scheduling and permissions.
diff --git a/website/blog/2020-07-06-version-0.63.md b/website/blog/2020-07-06-version-0.63.md
index e24d9f3295f..a8abda1321e 100644
--- a/website/blog/2020-07-06-version-0.63.md
+++ b/website/blog/2020-07-06-version-0.63.md
@@ -61,9 +61,7 @@ import {Pressable, Text} from 'react-native';
;
```
-
- A simple example of a Pressable component in action
-
+A simple example of a Pressable component in action
You can learn more about it from [the documentation](https://reactnative.dev/docs/pressable).
@@ -85,10 +83,7 @@ import {Text, PlatformColor} from 'react-native';
;
```
-
- Sets the color of the Text component to labelColor as defined by
- iOS.
-
+Sets the color of the Text component to labelColor as defined by iOS.
Android, on the other hand, [provides colors like colorButtonNormal](https://developer.android.com/reference/android/R.attr#colorButtonNormal). You can use this color in React Native with:
@@ -103,10 +98,7 @@ import {View, Text, PlatformColor} from 'react-native';
;
```
-
- Sets the background color of the View component to
- colorButtonNormal as defined by Android.
-
+Sets the background color of the View component to colorButtonNormal as defined by Android.
You can learn more about `PlatformColor` from [the documentation](https://reactnative.dev/docs/platformcolor). You can also check the actual [code examples present in the RNTester](https://github.com/facebook/react-native/blob/master/packages/rn-tester/js/examples/PlatformColor/PlatformColorExample.js).
@@ -125,9 +117,7 @@ const customDynamicTextColor = DynamicColorIOS({
;
```
-
- Changes the text color based on the system theme
-
+Changes the text color based on the system theme
You can learn more about `DynamicColorIOS` from [the documentation](https://reactnative.dev/docs/dynamiccolorios).
diff --git a/website/versioned_docs/version-0.70/appregistry.md b/website/versioned_docs/version-0.70/appregistry.md
index 5f3c1a22e48..7931ed524e2 100644
--- a/website/versioned_docs/version-0.70/appregistry.md
+++ b/website/versioned_docs/version-0.70/appregistry.md
@@ -5,9 +5,7 @@ title: AppRegistry
Project with Native Code Required
-
- If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
-
+
If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
diff --git a/website/versioned_docs/version-0.70/debugging.md b/website/versioned_docs/version-0.70/debugging.md
index d25c62987d7..fb6e8b5f9d1 100644
--- a/website/versioned_docs/version-0.70/debugging.md
+++ b/website/versioned_docs/version-0.70/debugging.md
@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging
-
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
-
+
Projects with Native Code Only
+ The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
If you want to enable deep links in your app, please read the below guide:
diff --git a/website/versioned_docs/version-0.70/permissionsandroid.md b/website/versioned_docs/version-0.70/permissionsandroid.md
index 76fab323a6b..b2633fdbeea 100644
--- a/website/versioned_docs/version-0.70/permissionsandroid.md
+++ b/website/versioned_docs/version-0.70/permissionsandroid.md
@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con
Project with Native Code Required
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
diff --git a/website/versioned_docs/version-0.70/pushnotificationios.md b/website/versioned_docs/version-0.70/pushnotificationios.md
index e2d15b4a3af..2239147d7c4 100644
--- a/website/versioned_docs/version-0.70/pushnotificationios.md
+++ b/website/versioned_docs/version-0.70/pushnotificationios.md
@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
Handle push notifications for your app, including permission handling and icon badge number.
diff --git a/website/versioned_docs/version-0.71/appregistry.md b/website/versioned_docs/version-0.71/appregistry.md
index 4db609c8fbd..fc0b4157857 100644
--- a/website/versioned_docs/version-0.71/appregistry.md
+++ b/website/versioned_docs/version-0.71/appregistry.md
@@ -5,9 +5,7 @@ title: AppRegistry
Project with Native Code Required
-
- If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
-
+
If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
diff --git a/website/versioned_docs/version-0.71/debugging.md b/website/versioned_docs/version-0.71/debugging.md
index 415a40cb411..7036f155886 100644
--- a/website/versioned_docs/version-0.71/debugging.md
+++ b/website/versioned_docs/version-0.71/debugging.md
@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
# Native Debugging
-
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
-
+
Projects with Native Code Only
+ The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
If you want to enable deep links in your app, please read the below guide:
diff --git a/website/versioned_docs/version-0.71/permissionsandroid.md b/website/versioned_docs/version-0.71/permissionsandroid.md
index 963b1d2a7d1..2972e8dbf7f 100644
--- a/website/versioned_docs/version-0.71/permissionsandroid.md
+++ b/website/versioned_docs/version-0.71/permissionsandroid.md
@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con
Project with Native Code Required
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
diff --git a/website/versioned_docs/version-0.71/pushnotificationios.md b/website/versioned_docs/version-0.71/pushnotificationios.md
index 665a50fbe54..f2ed4f1694e 100644
--- a/website/versioned_docs/version-0.71/pushnotificationios.md
+++ b/website/versioned_docs/version-0.71/pushnotificationios.md
@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
Handle push notifications for your app, including permission handling and icon badge number.
diff --git a/website/versioned_docs/version-0.72/appregistry.md b/website/versioned_docs/version-0.72/appregistry.md
index 4db609c8fbd..fc0b4157857 100644
--- a/website/versioned_docs/version-0.72/appregistry.md
+++ b/website/versioned_docs/version-0.72/appregistry.md
@@ -5,9 +5,7 @@ title: AppRegistry
Project with Native Code Required
-
- If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
-
+
If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
diff --git a/website/versioned_docs/version-0.72/linking.md b/website/versioned_docs/version-0.72/linking.md
index 9c256891daa..74cfd7eab16 100644
--- a/website/versioned_docs/version-0.72/linking.md
+++ b/website/versioned_docs/version-0.72/linking.md
@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
If you want to enable deep links in your app, please read the below guide:
diff --git a/website/versioned_docs/version-0.72/native-debugging.md b/website/versioned_docs/version-0.72/native-debugging.md
index 36638ef3d7a..e61b1fc58ca 100644
--- a/website/versioned_docs/version-0.72/native-debugging.md
+++ b/website/versioned_docs/version-0.72/native-debugging.md
@@ -6,10 +6,8 @@ title: Native Debugging
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';
-
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
-
+
Projects with Native Code Only
+ The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
Project with Native Code Required
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
diff --git a/website/versioned_docs/version-0.72/pushnotificationios.md b/website/versioned_docs/version-0.72/pushnotificationios.md
index 665a50fbe54..f2ed4f1694e 100644
--- a/website/versioned_docs/version-0.72/pushnotificationios.md
+++ b/website/versioned_docs/version-0.72/pushnotificationios.md
@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
Handle push notifications for your app, including permission handling and icon badge number.
diff --git a/website/versioned_docs/version-0.73/appregistry.md b/website/versioned_docs/version-0.73/appregistry.md
index 4db609c8fbd..fc0b4157857 100644
--- a/website/versioned_docs/version-0.73/appregistry.md
+++ b/website/versioned_docs/version-0.73/appregistry.md
@@ -5,9 +5,7 @@ title: AppRegistry
Project with Native Code Required
-
- If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
-
+
If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
diff --git a/website/versioned_docs/version-0.73/linking.md b/website/versioned_docs/version-0.73/linking.md
index 9352e51ba2e..91912a5d856 100644
--- a/website/versioned_docs/version-0.73/linking.md
+++ b/website/versioned_docs/version-0.73/linking.md
@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
If you want to enable deep links in your app, please read the below guide:
diff --git a/website/versioned_docs/version-0.73/native-debugging.md b/website/versioned_docs/version-0.73/native-debugging.md
index 36638ef3d7a..e61b1fc58ca 100644
--- a/website/versioned_docs/version-0.73/native-debugging.md
+++ b/website/versioned_docs/version-0.73/native-debugging.md
@@ -6,10 +6,8 @@ title: Native Debugging
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';
-
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
-
+
Projects with Native Code Only
+ The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
Project with Native Code Required
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
diff --git a/website/versioned_docs/version-0.73/pushnotificationios.md b/website/versioned_docs/version-0.73/pushnotificationios.md
index 665a50fbe54..f2ed4f1694e 100644
--- a/website/versioned_docs/version-0.73/pushnotificationios.md
+++ b/website/versioned_docs/version-0.73/pushnotificationios.md
@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
Handle push notifications for your app, including permission handling and icon badge number.
diff --git a/website/versioned_docs/version-0.74/appregistry.md b/website/versioned_docs/version-0.74/appregistry.md
index 4db609c8fbd..fc0b4157857 100644
--- a/website/versioned_docs/version-0.74/appregistry.md
+++ b/website/versioned_docs/version-0.74/appregistry.md
@@ -5,9 +5,7 @@ title: AppRegistry
Project with Native Code Required
-
- If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
-
+
If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
diff --git a/website/versioned_docs/version-0.74/linking.md b/website/versioned_docs/version-0.74/linking.md
index 9352e51ba2e..91912a5d856 100644
--- a/website/versioned_docs/version-0.74/linking.md
+++ b/website/versioned_docs/version-0.74/linking.md
@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
If you want to enable deep links in your app, please read the below guide:
diff --git a/website/versioned_docs/version-0.74/native-debugging.md b/website/versioned_docs/version-0.74/native-debugging.md
index 36638ef3d7a..e61b1fc58ca 100644
--- a/website/versioned_docs/version-0.74/native-debugging.md
+++ b/website/versioned_docs/version-0.74/native-debugging.md
@@ -6,10 +6,8 @@ title: Native Debugging
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';
-
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
-
+
Projects with Native Code Only
+ The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
Project with Native Code Required
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
diff --git a/website/versioned_docs/version-0.74/pushnotificationios.md b/website/versioned_docs/version-0.74/pushnotificationios.md
index 9ec9fcab911..5b3bedff114 100644
--- a/website/versioned_docs/version-0.74/pushnotificationios.md
+++ b/website/versioned_docs/version-0.74/pushnotificationios.md
@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
Handle notifications for your app, including scheduling and permissions.
diff --git a/website/versioned_docs/version-0.75/appregistry.md b/website/versioned_docs/version-0.75/appregistry.md
index 4db609c8fbd..fc0b4157857 100644
--- a/website/versioned_docs/version-0.75/appregistry.md
+++ b/website/versioned_docs/version-0.75/appregistry.md
@@ -5,9 +5,7 @@ title: AppRegistry
Project with Native Code Required
-
- If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
-
+
If you are using the managed Expo workflow there is only ever one entry component registered with AppRegistry and it is handled automatically (or through registerRootComponent). You do not need to use this API.
`AppRegistry` is the JS entry point to running all React Native apps. App root components should register themselves with `AppRegistry.registerComponent`, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking `AppRegistry.runApplication`.
diff --git a/website/versioned_docs/version-0.75/debugging-native-code.md b/website/versioned_docs/version-0.75/debugging-native-code.md
index b44adedb0ee..7ef7e3eb7e7 100644
--- a/website/versioned_docs/version-0.75/debugging-native-code.md
+++ b/website/versioned_docs/version-0.75/debugging-native-code.md
@@ -6,10 +6,8 @@ title: Debugging Native Code
import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';
-
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
-
+
Projects with Native Code Only
+ The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on prebuild to use this API.
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
If you want to enable deep links in your app, please read the below guide:
diff --git a/website/versioned_docs/version-0.75/permissionsandroid.md b/website/versioned_docs/version-0.75/permissionsandroid.md
index 307f5d17411..89f06360ea7 100644
--- a/website/versioned_docs/version-0.75/permissionsandroid.md
+++ b/website/versioned_docs/version-0.75/permissionsandroid.md
@@ -5,9 +5,7 @@ title: PermissionsAndroid
Project with Native Code Required
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Permissions in the Expo documentation for the appropriate alternative.
`PermissionsAndroid` provides access to Android M's new permissions model. The so-called "normal" permissions are granted by default when the application is installed as long as they appear in `AndroidManifest.xml`. However, "dangerous" permissions require a dialog prompt. You should use this module for those permissions.
diff --git a/website/versioned_docs/version-0.75/pushnotificationios.md b/website/versioned_docs/version-0.75/pushnotificationios.md
index 9ec9fcab911..5b3bedff114 100644
--- a/website/versioned_docs/version-0.75/pushnotificationios.md
+++ b/website/versioned_docs/version-0.75/pushnotificationios.md
@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'
Projects with Native Code Only
-
- The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
-
+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on Notifications in the Expo documentation for the appropriate alternative.
Handle notifications for your app, including scheduling and permissions.