Fix links

.github/workflows/check-links.yml

@@ -3,8 +3,8 @@ name: Check links
 on:
   pull_request:
     paths:
-      - "*.rs"
-      - "*.prdoc"
+      - "**.rs"
+      - "**.prdoc"
       - ".github/workflows/check-links.yml"
       - ".config/lychee.toml"
     types: [opened, synchronize, reopened, ready_for_review]

docs/sdk/src/polkadot_sdk/substrate.rs

@@ -99,7 +99,7 @@
 //!   demonstration.
 //!     * [`chain_spec_builder`]: Utility to build more detailed chain-specs for the aforementioned
 //!       node. Other projects typically contain a `build-spec` subcommand that does the same.
-//! * [`node_template`](https://github.com/paritytech/polkadot-sdk/tree/master/substrate/bin/node-template):
+//! * [`node_template`](https://github.com/paritytech/polkadot-sdk/tree/master/substrate/bin/node):
 //!   a template node that contains a minimal set of features and can act as a starting point of a
 //!   project.
 //! * [`subkey`]: Substrate's key management utility.

docs/sdk/src/polkadot_sdk/templates.rs

@@ -22,9 +22,8 @@
 //! - [`frontier-parachain-template`](https://github.com/paritytech/frontier-parachain-template): A
 //!   parachain template for launching EVM-compatible parachains.
 //!
-//! [`substrate-node-template`]: https://github.com/paritytech/polkadot-sdk/blob/master/substrate/bin/node-template/
-//! [`substrate-minimal-template`]: https://github.com/paritytech/polkadot-sdk/blob/master/substrate/bin/minimal/
-//! [`cumulus-parachain-template`]: https://github.com/paritytech/polkadot-sdk/blob/master/cumulus/parachain-template/
+//! [`minimal-template`]: https://github.com/paritytech/polkadot-sdk/blob/master/templates/minimal/
+//! [`parachain-template`]: https://github.com/paritytech/polkadot-sdk/blob/master/templates/parachain/
 
 // TODO: in general, we need to make a deliberate choice here of moving a few key templates to this
 // repo (nothing stays in `substrate-developer-hub`) and the everything else should be community

docs/sdk/src/reference_docs/runtime_vs_smart_contract.rs

@@ -117,7 +117,7 @@
 //! - **Contract Code Updates**: Once deployed, although typically immutable, Smart Contracts can be
 //!   upgraded, but lack of migration logic. The [pallet_contracts](../../../pallet_contracts/index.html)
 //!   allows for contracts to be upgraded by exposing the `set_code` dispatchable. More details on this
-//!   can be found in [Ink! documentation on upgradeable contracts](https://use.ink/5.x/basics/upgradeable-contracts).
+//!   can be found in [Ink! documentation on upgradeable contracts](https://use.ink/basics/upgradeable-contracts).
 //! - **Isolated Impact**: Upgrades or changes to a smart contract generally impact only that
 //!   contract and its users, unlike Runtime upgrades that have a network-wide effect.
 //! - **Simplicity and Rapid Development**: The development cycle for Smart Contracts is usually