Skip to content

Commit 3c53d8f

Browse files
committed
docs: update section numbers in README.md for clarity
1 parent ba2dda0 commit 3c53d8f

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -177,7 +177,7 @@ Add the following line to the end of the file.
177177
</p>
178178
</details>
179179

180-
### 2-1. Expo Setup
180+
### 3. Expo Setup
181181
For Expo projects, you can use the automated config plugin instead of manual setup.
182182

183183
**Add plugin to your Expo configuration:**
@@ -201,7 +201,7 @@ npx expo prebuild
201201
**Requirements**
202202
Expo SDK: 50.0.0 or higher
203203

204-
### 3. "CodePush-ify" Your App
204+
### 4. "CodePush-ify" Your App
205205

206206
The root component of your app should be wrapped with a higher-order component.
207207

@@ -245,7 +245,7 @@ export default CodePush({
245245
> The URL for fetching the release history should point to the resource location generated by the CLI tool.
246246
247247

248-
#### 3-1. Telemetry Callbacks
248+
#### 4-1. Telemetry Callbacks
249249

250250
Please refer to the [CodePushOptions](https://github.com/Soomgo-Mobile/react-native-code-push/blob/f0d26f7614af41c6dd4daecd9f7146e2383b2b0d/typings/react-native-code-push.d.ts#L76-L95) type for more details.
251251
- **onUpdateSuccess:** Triggered when the update bundle is executed successfully.
@@ -255,7 +255,7 @@ Please refer to the [CodePushOptions](https://github.com/Soomgo-Mobile/react-nat
255255
- **onSyncError:** Triggered when an unknown error occurs during the update process. (`CodePush.SyncStatus.UNKNOWN_ERROR` status)
256256

257257

258-
### 4. Configure the CLI Tool
258+
### 5. Configure the CLI Tool
259259

260260
> [!TIP]
261261
> For a more detailed and practical example, refer to the `CodePushDemoApp` in `example` directory. ([link](https://github.com/Soomgo-Mobile/react-native-code-push/tree/master/Examples/CodePushDemoApp))

0 commit comments

Comments
 (0)