diff --git a/neps/nep-0178.md b/neps/nep-0178.md index 7021c8f23..4c3405d26 100644 --- a/neps/nep-0178.md +++ b/neps/nep-0178.md @@ -131,7 +131,7 @@ Alice approves Market to transfer one of her tokens and passes `msg` so that NFT }' --accountId alice --depositYocto 1 ``` - At this point, near-cli will hang until the cross-contract call chain fully resolves, which would also be true if Alice used a Market frontend using [near-api-js](https://docs.near.org/tools/near-api-js/quick-reference). Alice's part is done, though. The rest happens behind the scenes. + At this point, near-cli will hang until the cross-contract call chain fully resolves, which would also be true if Alice used a Market frontend using [near-api](https://docs.near.org/tools/near-api). Alice's part is done, though. The rest happens behind the scenes. 2. `nft` schedules a call to `nft_on_approve` on `market`. Using near-cli notation for easy cross-reference with the above, this would look like: diff --git a/specs/ChainSpec/SelectingBlockProducers.md b/specs/ChainSpec/SelectingBlockProducers.md index 0c190dcf7..028ba3097 100644 --- a/specs/ChainSpec/SelectingBlockProducers.md +++ b/specs/ChainSpec/SelectingBlockProducers.md @@ -197,7 +197,7 @@ We sample validators with probability proportional to their stake using the foll - `weighted_sampler: WeightedIndex` - Allow $O(1)$ sampling - This structure will be based on the - [WeightedIndex](https://docs.rs/rand/latest/rand/distributions/struct.WeightedIndex.html) + [WeightedIndex](https://docs.rs/rand/latest/rand/distr/weighted/struct.WeightedIndex.html) implementation (see a description of [Vose's Alias Method](https://en.wikipedia.org/wiki/Alias_method) for details) diff --git a/specs/Standards/Tokens/MultiToken/ApprovalManagement.md b/specs/Standards/Tokens/MultiToken/ApprovalManagement.md index 6ecf60e00..ec14dbd16 100644 --- a/specs/Standards/Tokens/MultiToken/ApprovalManagement.md +++ b/specs/Standards/Tokens/MultiToken/ApprovalManagement.md @@ -98,7 +98,7 @@ Alice approves Market to transfer some of her tokens and passes `msg` so that MT "msg": "{\"action\": \"list\", \"price\": [\"100\",\"50\"],\"token\": \"nDAI\" }" }' --accountId alice --amount .000000000000000000000001 - At this point, near-cli will hang until the cross-contract call chain fully resolves, which would also be true if Alice used a Market frontend using [near-api-js](https://docs.near.org/tools/near-api-js/quick-reference). Alice's part is done, though. The rest happens behind the scenes. + At this point, near-cli will hang until the cross-contract call chain fully resolves, which would also be true if Alice used a Market frontend using [near-api](https://docs.near.org/tools/near-api). Alice's part is done, though. The rest happens behind the scenes. 2. `mt` schedules a call to `mt_on_approve` on `market`. Using near-cli notation for easy cross-reference with the above, this would look like: diff --git a/specs/Standards/Tokens/NonFungibleToken/ApprovalManagement.md b/specs/Standards/Tokens/NonFungibleToken/ApprovalManagement.md index c1407332e..92ac404fa 100644 --- a/specs/Standards/Tokens/NonFungibleToken/ApprovalManagement.md +++ b/specs/Standards/Tokens/NonFungibleToken/ApprovalManagement.md @@ -121,7 +121,7 @@ Alice approves Market to transfer one of her tokens and passes `msg` so that NFT }' --accountId alice --depositYocto 1 ``` - At this point, near-cli will hang until the cross-contract call chain fully resolves, which would also be true if Alice used a Market frontend using [near-api-js](https://docs.near.org/tools/near-api-js/quick-reference). Alice's part is done, though. The rest happens behind the scenes. + At this point, near-cli will hang until the cross-contract call chain fully resolves, which would also be true if Alice used a Market frontend using [near-api](https://docs.near.org/tools/near-api). Alice's part is done, though. The rest happens behind the scenes. 2. `nft` schedules a call to `nft_on_approve` on `market`. Using near-cli notation for easy cross-reference with the above, this would look like: