Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Corrected typos and grammar issues in README files #347

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
+3 −3
Open

Corrected typos and grammar issues in README files #347

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
6b8624d
typos README.md
Dimitrolito Dec 5, 2024
ede35a6
typos README.md
Dimitrolito Dec 5, 2024
1446192
Merge branch 'main' into fix/typos
nplasterer Dec 19, 2024
e032b48
Merge branch 'main' into fix/typos
nplasterer Dec 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ You can find the latest package version on [Maven Central](https://central.sonat

## Usage overview

The XMTP message API revolves around a message API client (client) that allows retrieving and sending messages to other XMTP network participants. A client must connect to a wallet app on startup. If this is the very first time the client is created, the client will generate a identity with a encrypted local database to store and retrieve messages. Each additional log in will create a new installation if a local database is not present.
The XMTP message API revolves around a message API client (client) that allows retrieving and sending messages to other XMTP network participants. A client must connect to a wallet app on startup. If this is the very first time the client is created, the client will generate an identity with an encrypted local database to store and retrieve messages. Each additional log in will create a new installation if a local database is not present.

```kotlin
// You'll want to replace this with a wallet from your application.
Expand Down
4 changes: 2 additions & 2 deletions library/src/main/java/org/xmtp/android/library/push/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Now that you have an FCM server set up, take a look at the `kotlin` folder in th

These files can serve as the basis for what you might want to provide for your own notification server. This proto code from the example notification server has already been generated and add in the `xmtp-android` example app if you use the example notification server as is.

**To run a example notification server:**
**To run an example notification server:**

1. Clone the [example-notification-server-go](https://github.com/xmtp/example-notification-server-go) repo.

Expand Down Expand Up @@ -112,4 +112,4 @@ These files can serve as the basis for what you might want to provide for your o
XMTPPush(context, "10.0.2.2:8080").unsubscribe(conversations.map { it.topic })
```

8. See example in [PushNotificationsService](https://github.com/xmtp/xmtp-android/blob/main/example/src/main/java/org/xmtp/android/example/pushnotifications/PushNotificationsService.kt) for how to decrypt the different messages.
8. See example in [PushNotificationsService](https://github.com/xmtp/xmtp-android/blob/main/example/src/main/java/org/xmtp/android/example/pushnotifications/PushNotificationsService.kt) for how to decrypt the different messages.