diff --git a/docs/docs/authentication.md b/docs/docs/authentication.md index de16f9c3..4967a222 100644 --- a/docs/docs/authentication.md +++ b/docs/docs/authentication.md @@ -2,7 +2,7 @@ ## Geo Connect -The default and recommended way to authenticate is via Geo Connect. Geo Connect is dedicated application hosted by the GeoBrowser team. Through Geo Connect you can authenticate with your GeoBrowser account and use it to selectively delegate access to your private and public spaces. +The default and recommended way to authenticate is via Geo Connect. Geo Connect is a dedicated application hosted by the GeoBrowser team. Through Geo Connect you can authenticate with your GeoBrowser account and use it to selectively delegate access to your private and public spaces. If you create you application using TypeSync or use the [hypergraph-app-template](https://github.com/graphprotocol/hypergraph-app-template) the full authentication flow is already implemented for you. diff --git a/docs/docs/key-features.md b/docs/docs/key-features.md index 4d69de61..d83b8fff 100644 --- a/docs/docs/key-features.md +++ b/docs/docs/key-features.md @@ -36,7 +36,7 @@ Data is **persisted first on the client**—not on a remote database. Users can Every update is encrypted **on the client** using XChaCha20-Poly1305. Only members of a Space possess the symmetric key, so neither the sync server nor The Graph can read private data. -* **Automatic key rotation** when members join/leave (not yet implemented). +* **Automatic key rotation**: when members join/leave (not yet implemented). * **Multi-device**: each device holds its own key pair. ## Knowledge Graph SDK diff --git a/docs/docs/mapping.md b/docs/docs/mapping.md index 7c89f770..2f3e0011 100644 --- a/docs/docs/mapping.md +++ b/docs/docs/mapping.md @@ -4,7 +4,7 @@ The public knowledge graph is based on property IDs. In order to integrate with This is done using an object called a mapping. The mapping has to be provided to the `HypergraphAppProvider` component. -A mapping entry defined the type IDs, properties and relations of a type. Here an example mapping for a schema with an `Event` and a `Company`: +A mapping entry defines the type IDs, properties and relations of a type. Here is an example mapping for a schema with an `Event` and a `Company`: ```tsx export const mapping: Mapping = { diff --git a/docs/docs/providers.md b/docs/docs/providers.md index 75ba1143..e3f1fcdf 100644 --- a/docs/docs/providers.md +++ b/docs/docs/providers.md @@ -56,7 +56,7 @@ const App = () => { ## HypergraphSpaceProvider -Whenever interact with a space you need to provide the space ID. In order providing the space ID to every hook e.g. useSpace, useQuery, useCreateEntity, etc. you can use the `HypergraphSpaceProvider` to wrap a section of your app with the space ID. +Whenever you interact with a space you need to provide the space ID. In order providing the space ID to every hook e.g. useSpace, useQuery, useCreateEntity, etc. you can use the `HypergraphSpaceProvider` to wrap a section of your app with the space ID. ```tsx import { HypergraphSpaceProvider } from "@graphprotocol/hypergraph-react"; diff --git a/docs/docs/publishing-public-data.md b/docs/docs/publishing-public-data.md index 034ee91b..4175baa0 100644 --- a/docs/docs/publishing-public-data.md +++ b/docs/docs/publishing-public-data.md @@ -80,6 +80,6 @@ const MyComponent = ({ publicSpaceId }: { publicSpaceId: string }) => { In order to explore the knowledge graph you can use GeoBrowser. -Visist [https://testnet.geobrowser.io/root](https://testnet.geobrowser.io/root) and explore the knowledge graph. Once you published you can find it via the search by name or by id. +Visit [https://testnet.geobrowser.io/root](https://testnet.geobrowser.io/root) and explore the knowledge graph. Once you published you can find it via the search by name or by id. -By looking up the data you also can verify that it was published correctly. \ No newline at end of file +By looking up the data you also can verify that it was published correctly. diff --git a/docs/docs/query-private-data.md b/docs/docs/query-private-data.md index f4ac0821..65fd3123 100644 --- a/docs/docs/query-private-data.md +++ b/docs/docs/query-private-data.md @@ -1,6 +1,6 @@ # Query Private Data -Based on your schema, you can query private data that your created using Hypergraph. +Based on your schema, you can query private data that you created using Hypergraph. ## useQuery diff --git a/docs/docs/query-public-data.md b/docs/docs/query-public-data.md index e83232ac..81602b92 100644 --- a/docs/docs/query-public-data.md +++ b/docs/docs/query-public-data.md @@ -1,6 +1,6 @@ # Query Public Data -Based on your schema, you can query public data that your created using Hypergraph. It works very much like [querying private data](/docs/query-private-data). +Based on your schema, you can query public data that you created using Hypergraph. It works very much like [querying private data](/docs/query-private-data). ## useQuery diff --git a/docs/docs/schema.md b/docs/docs/schema.md index 8f2ecef5..3321d58f 100644 --- a/docs/docs/schema.md +++ b/docs/docs/schema.md @@ -1,6 +1,6 @@ # Schema -The Hypergraph schema allows you define the data model for your application. It is based on the GRC-20 specification and allows you to define Types with properties and relations to other Types. +The Hypergraph schema allows you to define the data model for your application. It is based on the GRC-20 specification and allows you to define Types with properties and relations to other Types. ## Example diff --git a/docs/docs/space-invitations.md b/docs/docs/space-invitations.md index 9dee1882..7fdd712d 100644 --- a/docs/docs/space-invitations.md +++ b/docs/docs/space-invitations.md @@ -23,7 +23,7 @@ const { listInvitations } = useHypergraphApp(); listInvitations(); ``` -Once the functions is called the invitations are requested from and are available in the Hypergraph store. +Once the function is called the invitations are requested from and are available in the Hypergraph store. ```tsx import { useSelector } from "@xstate/store/react";