fixes (#1074)

Author: bucanero

docs/concepts/data-collections.md

@@ -252,7 +252,7 @@ map.getSome(key)
 
 [ [SDK source](https://github.com/near/near-sdk-rs/blob/master/near-sdk/src/collections/vector.rs) ]
 
-[ [Implementation](https://docs.rs/near-sdk/latest/near_sdk/collections/struct.Vector.html) ]
+[ [Implementation](https://docs.rs/near-sdk/latest/near_sdk/collections/vector/struct.Vector.html) ]
 
 ---
 
@@ -350,7 +350,7 @@ pub fn get_unordered_map(&self, key: String) -> String {
 
 [ [SDK source](https://github.com/near/near-sdk-rs/tree/master/near-sdk/src/collections/unordered_map) ]
 
-[ [Implementation](https://docs.rs/near-sdk/latest/near_sdk/collections/struct.UnorderedMap.html) ]
+[ [Implementation](https://docs.rs/near-sdk/latest/near_sdk/collections/unordered_map/struct.UnorderedMap.html) ]
 
 ---
 

docs/develop/contracts/rust/testing.md

@@ -6,7 +6,6 @@ sidebar_label: Testing
 
 There are a couple of ways to test Rust smart contracts in NEAR.
 - [Unit tests](#unit-tests)
-- [Simulation tests](#simulation-tests)
 - [End-to-end tests](#end-to-end-tests)
 
 This document will cover the first two in detail, and link to various code examples to refer to. Keep in mind that there are some simple examples located at <a href="https://near.dev" target="_blank">our examples page</a> that implement these tests.
@@ -121,17 +120,7 @@ The `--nocapture` flag will make sure that output from assertions and macros lik
 
 In summary, unit tests are a great way to make sure that the methods and data structures in your smart contract are working as intended.
 
-## Simulation tests {#simulation-tests}
-
-Within [`near-sdk-rs`](https://github.com/near/near-sdk-rs) there is a library [`near-sdk-sim`](https://github.com/near/near-sdk-rs/tree/master/near-sdk-sim) that allows simulation testing for Rust smart contracts.  With this utility you can:
-
-- Test cross-contract calls
-- Profile gas & storage usage for your contract
-- Inspect intermediate state of all calls within complex transactions
-
-For a step-by-step guide and more information, see the [README](https://github.com/near/near-sdk-rs/tree/master/near-sdk-sim) file for `near-sdk-sim`.
-
-  ## End-to-end tests
+## End-to-end tests
 
 This is where the rubber meets the road. End-to-end tests will help determine if the application is behaving as expected allowing us to see the entire flow of an app from start to finish. Unlike the previously mentioned tests, here we will use a live network (i.e. "testnet") (with actual tokens) to view (in real time) how our code behaves and any problems we may encounter. There many are testing applications that can accomplish this, but for our purposes we will focus on the [Jest testing suite](https://jestjs.io/).
 

docs/tutorials/contracts/nfts/minting-nfts.md

@@ -62,11 +62,10 @@ NFT Storage offers free decentralized storage and bandwidth for NFTs on [IPFS](h
 
 ## Non-fungible Token contract {#non-fungible-token-contract}
 
-[This repository](https://github.com/near-examples/NFT) includes an example implementation of a [non-fungible token] contract which uses [near-contract-standards] and [simulation] tests.
+[This repository](https://github.com/near-examples/NFT) includes an example implementation of a [non-fungible token] contract which uses [near-contract-standards] and simulation tests.
 
 [non-fungible token]: https://nomicon.io/Standards/NonFungibleToken
 [near-contract-standards]: https://github.com/near/near-sdk-rs/tree/master/near-contract-standards
-[simulation]: https://github.com/near/near-sdk-rs/tree/master/near-sdk-sim
 
 ### Clone the NFT repository {#clone-the-nft-repository}