Skip to content

Commit ad3db73

Browse files
committed
Update setup name
1 parent 37f757e commit ad3db73

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

OneSignalExample/Assets/OneSignal/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ There are two methods of installation available for the OneSignal Unity SDK:
6363
![onesignal unity sdk in my assets](Documentation/asset_listing.png)
6464

6565
4. A prompt to import all of the files of the OneSignal Unity SDK will appear. Click **Import** to continue and compile the scripts into your project.
66-
5. Navigate to **Window > OneSignal** (or follow the popup if upgrading) in the Unity Editor which will bring up a window with some final steps which need
66+
5. Navigate to **Window > OneSignal SDK Setup** (or follow the popup if upgrading) in the Unity Editor which will bring up a window with some final steps which need
6767
to be completed in order to finalize the installation. The most important of these steps is **Import OneSignal packages**.
6868

6969
> *Depending on your project configuration and if you are upgrading from a previous version, some of these steps may already be marked as "completed"*
@@ -90,7 +90,7 @@ There are two methods of installation available for the OneSignal Unity SDK:
9090
and click **Save**.
9191
3. Open the **Window > Package Manager** and switch to **My Registries** via the **Packages:** dropdown menu. You will see all of the OneSignal Unity SDK packages available
9292
on which you can then click **Install** for the platforms you would like to include. Dependencies will be added automatically.
93-
4. Once the packages have finished importing you will find a new menu under **Window > OneSignal**. Open it and you will find some final steps which need to be completed
93+
4. Once the packages have finished importing you will find a new menu under **Window > OneSignal SDK Setup**. Open it and you will find some final steps which need to be completed
9494
in order to finalize the installation.
9595
9696
> *Depending on your project configuration and if you are upgrading from a previous version, some of these steps may already be marked as "completed"*

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ There are two methods of installation available for the OneSignal Unity SDK:
6363
![onesignal unity sdk in my assets](Documentation/asset_listing.png)
6464

6565
4. A prompt to import all of the files of the OneSignal Unity SDK will appear. Click **Import** to continue and compile the scripts into your project.
66-
5. Navigate to **Window > OneSignal** (or follow the popup if upgrading) in the Unity Editor which will bring up a window with some final steps which need
66+
5. Navigate to **Window > OneSignal SDK Setup** (or follow the popup if upgrading) in the Unity Editor which will bring up a window with some final steps which need
6767
to be completed in order to finalize the installation. The most important of these steps is **Import OneSignal packages**.
6868

6969
> *Depending on your project configuration and if you are upgrading from a previous version, some of these steps may already be marked as "completed"*
@@ -90,7 +90,7 @@ There are two methods of installation available for the OneSignal Unity SDK:
9090
and click **Save**.
9191
3. Open the **Window > Package Manager** and switch to **My Registries** via the **Packages:** dropdown menu. You will see all of the OneSignal Unity SDK packages available
9292
on which you can then click **Install** for the platforms you would like to include. Dependencies will be added automatically.
93-
4. Once the packages have finished importing you will find a new menu under **Window > OneSignal**. Open it and you will find some final steps which need to be completed
93+
4. Once the packages have finished importing you will find a new menu under **Window > OneSignal SDK Setup**. Open it and you will find some final steps which need to be completed
9494
in order to finalize the installation.
9595
9696
> *Depending on your project configuration and if you are upgrading from a previous version, some of these steps may already be marked as "completed"*

0 commit comments

Comments
 (0)