From 4eef87fdd234620ff95d705098e5843dcd1837c8 Mon Sep 17 00:00:00 2001 From: lewinskimaciej Date: Wed, 5 Jun 2024 13:04:27 +0200 Subject: [PATCH] chore: grammar, typos --- pages/service/transactions/custom-charges.mdx | 2 +- pages/service/transactions/introduction.mdx | 2 +- pages/service/transactions/profile-paid-transactions.mdx | 4 ++-- pages/service/transactions/sponsored-transactions.mdx | 6 +++--- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/pages/service/transactions/custom-charges.mdx b/pages/service/transactions/custom-charges.mdx index 17054e8..d4e374f 100644 --- a/pages/service/transactions/custom-charges.mdx +++ b/pages/service/transactions/custom-charges.mdx @@ -35,7 +35,7 @@ const transaction = await beam.assetsV2.transferAssetV2("your-sender-id", { // } ``` -### Alternative methods of handling transactionHash +### Alternative methods of handling transactions - [Sponsored transactions](/service/transactions/sponsored-transactions): Learn about sponsored transactions for your users - [Profile-paid transactions](/service/transactions/profile-paid-transactions): Learn about how to make a profile pay for it's own transactions through BEAM diff --git a/pages/service/transactions/introduction.mdx b/pages/service/transactions/introduction.mdx index e57fbaf..9757eb3 100644 --- a/pages/service/transactions/introduction.mdx +++ b/pages/service/transactions/introduction.mdx @@ -6,7 +6,7 @@ title: Transactions Through Profiles, you were able to create a bunch of in-game accounts for your users and your own utility purposes. We've also explained how these in-game accounts can be funded with assets through minting - but before we dive into managing those assets within the profiles, it's good to have a general understanding about transactions. -Within the context of our sdk, a transaction is a transfer of assets of one profile to another - but since our underlying technology is blockchain, a transaction can also simply be explained as any on-chain transaction happening for your profiles (which are account abstractions) +Within the context of our SDK, a transaction is a transfer of assets from one profile to another - but since our underlying technology is blockchain, a transaction can also simply be explained as any on-chain transaction happening for your profiles (which are account abstractions). ### Transactions and gas diff --git a/pages/service/transactions/profile-paid-transactions.mdx b/pages/service/transactions/profile-paid-transactions.mdx index d158a20..9f6350c 100644 --- a/pages/service/transactions/profile-paid-transactions.mdx +++ b/pages/service/transactions/profile-paid-transactions.mdx @@ -4,7 +4,7 @@ title: Profile-paid transactions # Profile-paid transactions -An alternative to the default of sponsoring transactions, is to make the Profile pay for a transaction. This requires the profile to have enough BEAM in its possession to pay for the gas fees needed to handle the network transaction. This generally comes down to a very small sum of BEAM, but if you never distributed any BEAM to the Profiles that you've created, there's a big chance that none of the profiles actually have the required BEAM in place. +An alternative to the default of sponsoring transactions, is to make the Profile pay for a transaction. This requires the profile to have enough BEAM in its possession to pay for gas fees needed to handle the network transaction. This generally comes down to a very small amount of BEAM, but if you never distributed any BEAM to the Profiles that you've created, there's a big chance that none of the profiles actually have the required BEAM in place. In order to mitigate that, you could go different directions. Which is viable to you and your userbase completely depends on your context. @@ -39,7 +39,7 @@ const transaction = await beam.assetsV2.transferAssetV2("your-sender-id", { // } ``` -### Alternative methods of handling transactionHash +### Alternative methods of handling transactions - [Sponsored transactions](/service/transactions/sponsored-transactions): Learn about sponsored transactions for your users - [Custom charges](/service/transactions/custom-charges): A guide to managing and updating your game's assets and details within Beam. diff --git a/pages/service/transactions/sponsored-transactions.mdx b/pages/service/transactions/sponsored-transactions.mdx index ebed3bb..40cb0c7 100644 --- a/pages/service/transactions/sponsored-transactions.mdx +++ b/pages/service/transactions/sponsored-transactions.mdx @@ -8,9 +8,9 @@ By default, all transactions are **sponsored by you**. Sponsoring transactions m ### Why are transactions sponsored by default? -We think this default is sensible, as it's you as the game developer are in control of when a transaction happens. We consider it your responsibility as a game developer to create a viable economic model where sponsored and self-paid transactions (through BEAM or custom charges) go hand in hand to create the best experience for the gamer. +We think this default is sensible, as it's you as the game developer who is in control of when a transaction happens. We consider it your responsibility as a game developer to create a viable economic model where sponsored and self-paid transactions (through BEAM or custom charges) go hand in hand to create the best experience for the gamer. -To paint a clearer picture on how this looks like, below you'll find a transaction which is sponsored +To paint a better picture on how this looks like, below you'll find a transaction which is sponsored ```typescript const transaction = await beam.assetsV2.transferAssetV2("your-sender-id", { @@ -32,7 +32,7 @@ const transaction = await beam.assetsV2.transferAssetV2("your-sender-id", { // } ``` -### Alternative methods of handling transactionHash +### Alternative methods of handling transactions - [Profile-paid transactions](/service/transactions/profile-paid-transactions): Learn about how to make a profile pay for it's own transactions through BEAM - [Custom charges](/service/transactions/custom-charges): A guide to managing and updating your game's assets and details within Beam.