diff --git a/near-contract-standards/src/lib.rs b/near-contract-standards/src/lib.rs
index 3a3b86d73..def692583 100644
--- a/near-contract-standards/src/lib.rs
+++ b/near-contract-standards/src/lib.rs
@@ -2,9 +2,9 @@
 #![allow(clippy::missing_const_for_fn, clippy::redundant_pub_crate)]
 #![allow(clippy::needless_lifetimes)]
 
-/// Fungible tokens as described in [by the spec](https://nomicon.io/Standards/FungibleToken/README.html).
+/// Fungible tokens as described in [by the spec](https://nomicon.io/Standards/Tokens/FungibleToken).
 pub mod fungible_token;
-/// Non-fungible tokens as described in [by the spec](https://nomicon.io/Standards/NonFungibleToken/README.html).
+/// Non-fungible tokens as described in [by the spec](https://nomicon.io/Standards/Tokens/NonFungibleToken).
 pub mod non_fungible_token;
 /// Storage management deals with handling [state storage](https://docs.near.org/docs/concepts/storage-staking) on NEAR. This follows the [storage management standard](https://nomicon.io/Standards/StorageManagement.html).
 pub mod storage_management;
diff --git a/near-sdk/src/store/mod.rs b/near-sdk/src/store/mod.rs
index ec724474a..ad1f3c5f7 100644
--- a/near-sdk/src/store/mod.rs
+++ b/near-sdk/src/store/mod.rs
@@ -20,8 +20,8 @@
 //! If your collection has up to 100 entries, it's acceptable to use the native collection, as it might be simpler
 //! since you don't have to manage prefixes as we do with near collections.
 //! However, if your collection has 1,000 or more entries, it's better to use a near collection. The investigation
-//! mentioned above shows that running the contains method on a native HashSet<i32> consumes 41% more gas
-//! compared to a near IterableSet<i32>.
+//! mentioned above shows that running the contains method on a native [`std::collections::HashSet<i32>`] consumes 41% more gas
+//! compared to a near [`crate::store::IterableSet<i32>`].
 //!
 //! It's also a bad practice to have a native collection properties as a top level properties of your contract.
 //! The contract will load all the properties before the contract method invocation. That means that all your native
@@ -52,7 +52,7 @@
 //! - [`UnorderedMap`]: Storage version of [`std::collections::HashMap`]. No ordering
 //!   guarantees.
 //!
-//! - [`TreeMap`](TreeMap) (`unstable`): Storage version of [`std::collections::BTreeMap`]. Ordered by key,
+//! - [`TreeMap`] (`unstable`): Storage version of [`std::collections::BTreeMap`]. Ordered by key,
 //!   which comes at the cost of more expensive lookups and iteration.
 //!
 //! Sets:
diff --git a/near-sdk/src/test_utils/context.rs b/near-sdk/src/test_utils/context.rs
index 07766d6f4..45823aa69 100644
--- a/near-sdk/src/test_utils/context.rs
+++ b/near-sdk/src/test_utils/context.rs
@@ -65,7 +65,7 @@ pub struct VMContext {
     pub random_seed: [u8; 32],
     /// If Some, it means that execution is made in a view mode and defines its configuration.
     /// View mode means that only read-only operations are allowed.
-    /// See <https://nomicon.io/Proposals/0018-view-change-method.html> for more details.
+    /// See <https://nomicon.io/Proposals/view-change-method> for more details.
     pub view_config: Option<ViewConfig>,
     /// How many `DataReceipt`'s should receive this execution result. This should be empty if
     /// this function call is a part of a batch and it is not the last action.
diff --git a/near-sdk/src/test_utils/mod.rs b/near-sdk/src/test_utils/mod.rs
index 02f2fea2b..b305c0c98 100644
--- a/near-sdk/src/test_utils/mod.rs
+++ b/near-sdk/src/test_utils/mod.rs
@@ -19,7 +19,7 @@ pub use context::{accounts, testing_env_with_promise_results, VMContextBuilder};
 ///   about the VM to configure parameters not directly related to the transaction being executed.
 /// - `fee_config`(optional): [`RuntimeFeesConfig`] which configures the
 ///   fees for execution and storage of transactions.
-/// - `validators`(optional): a [`HashMap`]<[`AccountId`], [`Balance`]> mocking the
+/// - `validators`(optional): a [`HashMap`]<[`AccountId`], [`NearToken`]> mocking the
 ///   current validators of the blockchain.
 /// - `promise_results`(optional): a [`Vec`] of [`PromiseResult`] which mocks the results
 ///   of callback calls during the execution.
@@ -57,7 +57,7 @@ pub use context::{accounts, testing_env_with_promise_results, VMContextBuilder};
 /// [`vm::Config`]: near_parameters::vm::Config
 /// [`RuntimeFeesConfig`]: near_parameters::RuntimeFeesConfig
 /// [`AccountId`]: crate::AccountId
-/// [`Balance`]: crate::Balance
+/// [`NearToken`]: crate::NearToken
 /// [`PromiseResult`]: crate::PromiseResult
 /// [`HashMap`]: std::collections::HashMap
 #[macro_export]
diff --git a/near-sdk/src/test_utils/test_env.rs b/near-sdk/src/test_utils/test_env.rs
index 15b789fcd..670b40029 100644
--- a/near-sdk/src/test_utils/test_env.rs
+++ b/near-sdk/src/test_utils/test_env.rs
@@ -32,7 +32,7 @@ pub fn setup() {
 }
 
 /// free == effectively unlimited gas
-/// Sets up the blockchain interface with a [`VMConfig`] which sets the gas costs to zero.
+/// Sets up the blockchain interface with a [`near_parameters::vm::Config`] which sets the gas costs to zero.
 pub fn setup_free() {
     let mut config = test_vm_config();
     config.make_free();