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

Jump to bottom

Fix typos, lets -> let's #498

Merged
merged 1 commit into from May 26, 2023
Merged

Fix typos, lets -> let's #498

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion blog/2023-01-10-ssi-chat-gpt.md
View file
Open in desktop
Expand Up @@ -31,7 +31,7 @@ The [SSI-SDK](https://github.com/TBD54566975/ssi-sdk) is an implementation of a

<!--truncate-->

Now there is a whole lot of (lets face it: tedious) machinery to get WASM to be compiled from Go (ok if you are really curious you can [read the code](https://github.com/TBD54566975/ssi-sdk/pull/265/)), but the upshot of it is that there is a .wasm file produced which when consumed in just the right way in a web page, allows you to call functions from JavaScript, that look and feel like JavaScript, but are actually running in the web-assembly machiner (and compiled down from Golang).
Now there is a whole lot of (let's face it: tedious) machinery to get WASM to be compiled from Go (ok if you are really curious you can [read the code](https://github.com/TBD54566975/ssi-sdk/pull/265/)), but the upshot of it is that there is a .wasm file produced which when consumed in just the right way in a web page, allows you to call functions from JavaScript, that look and feel like JavaScript, but are actually running in the web-assembly machiner (and compiled down from Golang).

Say you had a function in Golang land which looked like this:

Expand Down
4 changes: 2 additions & 2 deletions docs/web5/learn/decentralized-identifiers.md
View file
Open in desktop
Expand Up @@ -42,7 +42,7 @@ We need an identifier that isn't tied to a centralized authority, that we can ta

### Methods

Now that Alice and Bob know that they need a DID lets take a look at the different kinds of DIDs they can have.
Now that Alice and Bob know that they need a DID let's take a look at the different kinds of DIDs they can have.

There are lots of different implementations of DIDs (called [DID methods](https://www.w3.org/TR/did-core/#methods)) with different use cases. Web5 currently supports a few methods.

Expand All @@ -64,7 +64,7 @@ did:ion is a very robust, very decentralized platform for anchoring your DIDs. I

### DID Documents

Now that Alice and Bob have gone through one of the methods and they have their DIDs, they now need a DID document to store those DIDs. Lets learn about DID documents, what they are and what fields we might see in them.
Now that Alice and Bob have gone through one of the methods and they have their DIDs, they now need a DID document to store those DIDs. Let's learn about DID documents, what they are and what fields we might see in them.

#### What is it?

Expand Down
2 changes: 1 addition & 1 deletion docs/web5/learn/protocols.md
View file
Open in desktop
Expand Up @@ -32,7 +32,7 @@ Every protocol document has a few basic keys:

These terms are combined in a human-readable way to define both the data schema and permissions of your app.

To apply these concepts, lets consider if we wanted to build a basic social networking application. In our social network, we want users to be able to post images with captions that can be replied to, as well as messages with replies. This application has a data design of two key objects: images and messages. Images have caption and reply properties, while messages just have a replies property.
To apply these concepts, let's consider if we wanted to build a basic social networking application. In our social network, we want users to be able to post images with captions that can be replied to, as well as messages with replies. This application has a data design of two key objects: images and messages. Images have caption and reply properties, while messages just have a replies property.

Now let’s imagine how we’d construct the permissions for such an app. We want all users to be able to post images and messages, but we have a few constraints on the other properties:

Expand Down