Automated scrape: 2025-11-14 00:23:12

Author: github-actions[bot]

merged_docs/all_merged.md

@@ -1,4 +1,4 @@
-# Source: https://cadence-lang.org/docs/language/
+# Source: https://cadence-lang.org/docs/language
 
 The Cadence Programming Language | Cadence
 

merged_docs/essentials_merged.md

@@ -46,42 +46,40 @@ On this page
 
 # Account Linking
 
-Account linking is a unique Flow concept that enables sharing ownership over [accounts](/build/cadence/basics/accounts). In
-order to understand how we can achieve that we must first understand how accounts on Flow are accessed.
+Account linking is a unique Flow concept that allows sharing ownership over [accounts](/build/cadence/basics/accounts). To understand how we can achieve that, we must first understand how to access accounts on Flow.
 
-Accounts on flow can be accessed in Cadence through two types, `PublicAccount` and `Account`. As the name implies the
+You can access accounts on flow in Cadence through two types, `PublicAccount` and `Account`. As the name implies, the
 `PublicAccount` type gives access to all public account information such as address, balance, storage capacity, etc.,
 but doesn't allow changes to the account. The `Account` type (or more specifically, an
 [entitled](https://cadence-lang.org/docs/language/access-control#entitlements) `&Account`) allows the same access as
-`PublicAccount` but also allows changes to the account, including adding/revoking account keys, managing the deployed
+`PublicAccount` but also allows changes to the account, which includes adding or revoking account keys, managing the deployed
 contracts, as well as linking and publishing Capabilities.
 
 ![Flow account structure](/assets/images/account-structure-835ec18016e0f43c6b4a4fea2e54934f.png)
 
 ## Accessing Account[​](#accessing-account "Direct link to Accessing Account")
 
-Accessing `Account` allows for modification to account storage, so it's essential to safeguard this access by mandating
-that transactions are signed by the account being accessed. [Account
-entitlements](https://cadence-lang.org/docs/language/accounts/#performing-write-operations) enable for more granular
-access control over the specific parts of the account that can be accessed from within the signed transaction. A
+Accessing `Account` allows for modification to account storage, so it's essential to mandate that the account being accessed signs all transactions, which safeguards this access.
+[Account
+entitlements](https://cadence-lang.org/docs/language/accounts/#performing-write-operations) allow for more granular
+access control over the specific parts of the account that you can access from within the signed transaction. A
 transaction can list multiple authorizing account it wants to access as part of the `prepare` section of the
 transaction. Read more about transaction signing in the [transaction documentation](/build/cadence/basics/transactions).
 
-Since access to the `Account` object enables state change, the idea of account ownership actually translates to the
+Since access to the `Account` object allows state change, the idea of account ownership actually translates to the
 ability to access the underlying account. Traditionally, you might consider this the same as having key access on an
 account, but we'll see in just a minute how programmatic, ownership-level access is unlocked with [Capabilities on
 Flow](https://cadence-lang.org/docs/language/capabilities).
 
 ## Account Capabilities[​](#account-capabilities "Direct link to Account Capabilities")
 
-Before proceeding the reader will need a clear understanding of [Cadence
-capabilities](https://cadence-lang.org/docs/language/capabilities) to follow this section. Advanced features such as
-Account Capabilities are powerful but if used incorrectly can put your app or users at risk.
+Before you continue with this section, you'll need a clear understanding of [Cadence
+capabilities](https://cadence-lang.org/docs/language/capabilities). Advanced features such as
+Account Capabilities are powerful, but they can put your app or users at risk if used incorrectly.
 
-Cadence allows the creation of Capabilities to delegate access to account storage, meaning any account obtaining a valid
+Cadence allows for Capabilities creation to delegate access to account storage, which means any account that obtains a valid
 Ccapability to another account object in the storage can access it. This is a powerful feature on its own - accessing
-another account programmatically without the need for an active key on the accessible account. The access to the object
-can be limited when creating a Capability so only intended functions or fields can be accessed.
+another account programmatically without the need for an active key on the accessible account. You can limit the access to the object when you create a Capability so your users can only access intended functions or fields.
 
 Account linking is made possible by the extension of Capabilities on the `Account` object itself. Similar to how storage
 capabilities allow access to a value stored in an account's storage, `&Account` Capabilities allow delegated access to
@@ -91,13 +89,13 @@ This Capability can of course be revoked at any time by the delegating account.
 
 ### Creating Account Links[​](#creating-account-links "Direct link to Creating Account Links")
 
-When referring to 'account linking' we mean that an `&Account` Capability is created by the parent account and published
-to another account. The account owning the `&Account` Capability which was made available to another account is the child
+When we refer to 'account linking,' we mean that the parent account creates an `&Account` Capability and published
+to another account. The account that owns the `&Account` Capability which was made available to another account is the child
 account. The account in possession of the Capability given by the child account becomes its parent account.
 
 ![Account linking on Flow relational diagram](/assets/images/account-linking-relational-diagram-9ea0dedfb84460d27a1e78e2a6c40b65.png)
 
-A link between two existing accounts on Flow can be created in two steps:
+You can create a link between two existing accounts on Flow in two steps:
 
 1. A child account creates an `&Account` Capability and publishes it to the parent account.
 2. The parent account, claims that Capability and can access the child's account through it.
@@ -234,9 +232,9 @@ _18
 
 ## What is account linking most useful for?[​](#what-is-account-linking-most-useful-for "Direct link to What is account linking most useful for?")
 
-Account linking was specifically designed to enable smooth and seamless custodial onboarding of users to your Flow based
+Account linking was specifically designed to allow smooth and seamless custodial onboarding of users to your Flow based
 application without them first requiring a wallet to do so. This pattern overcomes both the technical hurdle, as well as
-user's reluctance to install a wallet, opening access to Flow applications to every user. Users can experience an app
+user's reluctance to install a wallet, which opens access to Flow applications to every user. Users can experience an app
 without any delay while still offering a path to self-sovreign ownership.
 
 Naturally, users may expect to use their account with another application, or otherwise move assets stored in that
@@ -245,7 +243,7 @@ account instead of the user and stores that user's specific state in the app-cre
 can take ownership of the app account providing they possess a full [Flow account](/build/cadence/basics/accounts), typically
 by installing a wallet app.
 
-Account linking enables users to possess multiple linked child accounts from different apps. Complexities associated
+Account linking allows users to possess multiple linked child accounts from different apps. Complexities associated
 with accessing those child accounts are eliminated by abstracting access to them through the user's parent account.
 
 info
@@ -258,46 +256,45 @@ already has access to the assets in the child account.
 
 ![Multiple parent-child accounts on Flow](/assets/images/account-linking-multiple-accounts-19cad9db0d1f1abdde126848033b3e43.png)
 
-This shared control over the digital items in the in-app account enables users to establish real ownership of the items
+This shared control over the digital items in the in-app account allows users to establish real ownership of the items
 beyond the context of the app, where they can use their parent account to view inventory, take the items to other apps
 in the ecosystem, such as a marketplace or a game.
 
-Most importantly, users are able to do this without the need to transfer the digital items between accounts, making it
-seamless to continue using the original app while also enjoying their assets in other contexts.
+Most importantly, users can do this without the need to transfer the digital items between accounts, which makes it
+seamless to continue using the original app and enjoy their assets in other contexts.
 
 ## Security Considerations[​](#security-considerations "Direct link to Security Considerations")
 
 Account linking is a *very* powerful Cadence feature, and thus it must be treated with care. So far in this document,
-we've discussed account linking between two accounts we own, even if the child account is managed by a third-party
-application. But, we can't make the same trust assumptions about custodial accounts in the real world.
+we've discussed account linking between two accounts we own, even if a third-party
+application manages the child account. But, we can't make the same trust assumptions about custodial accounts in the real world.
 
-Creating an `&Account` Capability and publishing it to an account we don't own means we are giving that account full
+If we create an `&Account` Capability and publish it to an account we don't own, we give that account full
 access to our account. This should be seen as an anti-pattern.
 
 warning
 
-Creating an `&Account` Capability and sharing it with third-party account effectually the same as giving that person your
+If you create an `&Account` Capability and share it with a third-party account, you effectively give that person your
 account's private keys.
 
 Because unfiltered account linking can be dangerous, Flow introduces the [`HybridCustody`
-contract](/blockchain-development-tutorials/cadence/account-management/parent-accounts) that helps custodial applications regulate access while enabling parent accounts to
+contract](/blockchain-development-tutorials/cadence/account-management/parent-accounts) that helps custodial applications regulate access and allows parent accounts to
 manage their many child accounts and assets within them.
 
 ## Hybrid Custody and Account Linking[​](#hybrid-custody-and-account-linking "Direct link to Hybrid Custody and Account Linking")
 
-Apps need assurances that their own resources are safe from malicious actors, so giving out full access might not be the
-form they want. Using hybrid custody contracts, the app still maintains control of their managed accounts, but they can:
+Apps need assurances that their own resources are safe from malicious actors, so to permit full access might not be what they want. Hybrid custody contracts will allow the app to maintain control of their managed accounts, but they can:
 
 1. Share capabilities freely, with a few built-in controls over the types of capabilities that can be retrieved by
-   parent accounts via helper contracts (the `CapabilityFactory`, and `CapabilityFilter`)
-2. Share additional capabilities (public or private) with a parent account via a `CapabilityDelegator` resource
+   parent accounts via helper contracts (the `CapabilityFactory`, and `CapabilityFilter`).
+2. Share additional capabilities (public or private) with a parent account via a `CapabilityDelegator` resource.
 
 Learn more about it in the [Hybrid Custody documentation](/blockchain-development-tutorials/cadence/account-management/parent-accounts).
 
 ### Guides[​](#guides "Direct link to Guides")
 
 * [Building Walletless Applications Using Child Accounts](/blockchain-development-tutorials/cadence/account-management/child-accounts) covers how apps can leverage Account
-  Linking to create a seamless user experience and enable future self-custody.
+  Linking to create a seamless user experience and allow future self-custody.
 * [Working With Parent Accounts](/blockchain-development-tutorials/cadence/account-management/parent-accounts) covers features enabled by the core `HybridCustody` contract to
   access child account assets from parent accounts. This is useful for apps like marketplaces or wallets that are
   working with accounts that have potential child accounts.
@@ -314,7 +311,7 @@ Learn more about it in the [Hybrid Custody documentation](/blockchain-developmen
 
 [Edit this page](https://github.com/onflow/docs/tree/main/docs/blockchain-development-tutorials/cadence/account-management/index.md)
 
-Last updated on **Sep 25, 2025** by **Brian Doyle**
+Last updated on **Nov 3, 2025** by **cshannon1218**
 
 [Previous