Skip to content

Commit bab5c58

Browse files
slorberslorber
authored
Fix double p tags (facebook#4267)
1 parent 36d4c42 commit bab5c58

36 files changed

+45
-125
lines changed

‎docs/appregistry.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,7 @@ title: AppRegistry
55

66
<div className="banner-native-code-required">
77
<h3>Project with Native Code Required</h3>
8-
<p>
9-
If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
10-
</p>
8+
<p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
119
</div>
1210

1311
`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`.

‎docs/debugging-native-code.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con
77

88
<div className="banner-native-code-required">
99
<h3>Projects with Native Code Only</h3>
10-
<p>
11-
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
12-
</p>
10+
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
1311
</div>
1412

1513
## Accessing Logs

‎docs/linking.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional
3030

3131
<div className="banner-native-code-required">
3232
<h3>Projects with Native Code Only</h3>
33-
<p>
34-
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
35-
</p>
33+
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
3634
</div>
3735

3836
If you want to enable deep links in your app, please read the below guide:

‎docs/permissionsandroid.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,7 @@ title: PermissionsAndroid
55

66
<div className="banner-native-code-required">
77
<h3>Project with Native Code Required</h3>
8-
<p>
9-
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
10-
</p>
8+
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
119
</div>
1210

1311
`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.

‎docs/pushnotificationios.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,7 @@ title: '🚧 PushNotificationIOS'
77
88
<div className="banner-native-code-required">
99
<h3>Projects with Native Code Only</h3>
10-
<p>
11-
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.
12-
</p>
10+
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/versions/latest/sdk/notifications/">Notifications</a> in the Expo documentation for the appropriate alternative.</p>
1311
</div>
1412

1513
Handle notifications for your app, including scheduling and permissions.

‎website/blog/2020-07-06-version-0.63.md‎

Lines changed: 4 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -61,9 +61,7 @@ import {Pressable, Text} from 'react-native';
6161
</Pressable>;
6262
```
6363

64-
<p className="snippet-caption">
65-
A simple example of a Pressable component in action
66-
</p>
64+
<p className="snippet-caption">A simple example of a Pressable component in action</p>
6765

6866
You can learn more about it from [the documentation](https://reactnative.dev/docs/pressable).
6967

@@ -85,10 +83,7 @@ import {Text, PlatformColor} from 'react-native';
8583
</Text>;
8684
```
8785

88-
<p className="snippet-caption">
89-
Sets the color of the Text component to labelColor as defined by
90-
iOS.
91-
</p>
86+
<p className="snippet-caption">Sets the color of the Text component to labelColor as defined by iOS.</p>
9287

9388
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:
9489

@@ -103,10 +98,7 @@ import {View, Text, PlatformColor} from 'react-native';
10398
</View>;
10499
```
105100

106-
<p className="snippet-caption">
107-
Sets the background color of the View component to
108-
colorButtonNormal as defined by Android.
109-
</p>
101+
<p className="snippet-caption">Sets the background color of the View component to colorButtonNormal as defined by Android.</p>
110102

111103
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).
112104

@@ -125,9 +117,7 @@ const customDynamicTextColor = DynamicColorIOS({
125117
</Text>;
126118
```
127119

128-
<p className="snippet-caption">
129-
Changes the text color based on the system theme
130-
</p>
120+
<p className="snippet-caption">Changes the text color based on the system theme</p>
131121

132122
You can learn more about `DynamicColorIOS` from [the documentation](https://reactnative.dev/docs/dynamiccolorios).
133123

‎website/versioned_docs/version-0.70/appregistry.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,7 @@ title: AppRegistry
55

66
<div className="banner-native-code-required">
77
<h3>Project with Native Code Required</h3>
8-
<p>
9-
If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.
10-
</p>
8+
<p>If you are using the managed Expo workflow there is only ever one entry component registered with <code>AppRegistry</code> and it is handled automatically (or through <a href="https://docs.expo.dev/versions/latest/sdk/register-root-component/">registerRootComponent</a>). You do not need to use this API.</p>
119
</div>
1210

1311
`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`.

‎website/versioned_docs/version-0.70/debugging.md‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -164,10 +164,8 @@ You can view installation instructions [in the README](https://github.com/infini
164164
# Native Debugging
165165

166166
<div className="banner-native-code-required">
167-
<h3>Projects with Native Code Only</h3>
168-
<p>
169-
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.
170-
</p>
167+
<h3>Projects with Native Code Only</h3><p>
168+
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/workflow/prebuild/" target="_blank">prebuild</a> to use this API.</p>
171169
</div>
172170

173171
## Accessing console logs

‎website/versioned_docs/version-0.70/linking.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,7 @@ As mentioned in the introduction, there are some URL schemes for core functional
3030

3131
<div className="banner-native-code-required">
3232
<h3>Projects with Native Code Only</h3>
33-
<p>
34-
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.
35-
</p>
33+
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/linking/">Linking</a> in the Expo documentation for the appropriate alternative.</p>
3634
</div>
3735

3836
If you want to enable deep links in your app, please read the below guide:

‎website/versioned_docs/version-0.70/permissionsandroid.md‎

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con
77

88
<div className="banner-native-code-required">
99
<h3>Project with Native Code Required</h3>
10-
<p>
11-
The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.
12-
</p>
10+
<p>The following section only applies to projects with native code exposed. If you are using the managed Expo workflow, see the guide on <a href="https://docs.expo.dev/guides/permissions/">Permissions</a> in the Expo documentation for the appropriate alternative.</p>
1311
</div>
1412

1513
`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.

0 commit comments

Comments
 (0)