Skip to content

Commit

Permalink
Minor Grammar Correction In Docs (3) (#2649)
Browse files Browse the repository at this point in the history
* Minor Grammar Correction In Docs (3)

Fix: 'principal account' -> 'a principal account'

* Update packages/apps/docs/src/docs/learn/accounts-keys.md

---------

Co-authored-by: Lisa Gunn <44206363+lsgunnlsgunn@users.noreply.github.com>
  • Loading branch information
0xTrip and lsgunnlsgunn authored Nov 21, 2024
1 parent befda17 commit f801f9a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion packages/apps/docs/src/docs/learn/accounts-keys.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ It's also important to remember that the account name doesn't determine ownershi

As mentioned in [Defining accounts](#defining-accounts), an account name can be any string. Using an arbitrary string as an account name can be convenient. For example, you might want to create an account with a name that identifies it as a personal or primary account, for example, Lola-Pistola, so that it's easy to differentiate it from an account that you own jointly with another party or a group, for example, Las-Pistolas.

However, using arbitrary account names like these examples can make your account vulnerable to certain kinds of attacks. For example, an attacker might try to hijack a transaction that creates an account or transfers funds by changing the guard associated with the account name. One way to prevent an account from being hijacked by an attacker is to create **principal** account. A principal is a way to enforce a one-to-one relationship between a guard and what the guard is there to protect, like the ownership of an account balance. If an attacker tries to hijack the account by changing the guard, the guard won't match the account as it's defined in the underlying ledger, so the guard would be rejected and the transaction would fail.
However, using arbitrary account names like these examples can make your account vulnerable to certain kinds of attacks. For example, an attacker might try to front-run a transaction that creates an account or transfers funds by changing the guard associated with the account name. One way to prevent an account from being hijacked by an attacker is to create a **principal** account. A principal is a way to enforce a one-to-one relationship between a guard and what the guard is there to protect, like the ownership of an account balance. If an attacker tries to hijack the account by changing the guard, the guard won't match the account as it's defined in the underlying ledger, so the guard would be rejected and the transaction would fail.

### Guards

Expand Down

0 comments on commit f801f9a

Please sign in to comment.