fix: Update additional broken polkadot.com documentation links

Replace more deprecated polkadot.com URLs (returning 404 after site
redesign) with current equivalents:

- favicon: Use existing paritytech PNG logo (ICO was removed)
- papers: polkadot.com/papers -> github.com/polkadot-io/polkadot-white-paper
- approval checking blog: polkadot.com/blog -> wiki.polkadot.com/docs

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>

Author: nkpar

docs/sdk/src/lib.rs

@@ -25,7 +25,7 @@
 #![warn(rustdoc::private_intra_doc_links)]
 // Frame macros reference features which this crate does not have
 #![allow(unexpected_cfgs)]
-#![doc(html_favicon_url = "https://polkadot.com/favicon.ico")]
+#![doc(html_favicon_url = "https://raw.githubusercontent.com/paritytech/polkadot-sdk/master/docs/images/Polkadot_Logo_Horizontal_Pink_White.png")]
 #![doc(
 	html_logo_url = "https://raw.githubusercontent.com/paritytech/polkadot-sdk/master/docs/images/Polkadot_Logo_Horizontal_Pink_White.png"
 )]

docs/sdk/src/polkadot_sdk/polkadot.rs

@@ -14,7 +14,7 @@
 //! 	- [Dashboard](https://polkadot-fellows.github.io/dashboard/)
 //! - [Polkadot Specs](http://spec.polkadot.network)
 //! - [The Polkadot Parachain Host Implementers' Guide](https://paritytech.github.io/polkadot-sdk/book/)
-//! - [Polkadot papers](https://polkadot.com/papers/)
+//! - [Polkadot papers](https://github.com/polkadot-io/polkadot-white-paper)
 //! - [JAM Graypaper](https://graypaper.com)
 //!
 //! ## Alternative Node Implementations 🌈
@@ -54,7 +54,7 @@
 //!   the validity of the block execution of multiple parachains using the same set of validators as
 //!   the Relay Chain. In practice, this means that the shards (parachains) share the same economic
 //!   security as the Relay Chain.
-//!   Learn about this process called [Approval Checking](https://polkadot.com/blog/polkadot-v1-0-sharding-and-economic-security#approval-checking-and-finality).
+//!   Learn about this process called [Approval Checking](https://wiki.polkadot.com/docs/learn-parachains-protocol).
 //! * A framework to build blockchains: In order to materialize the ecosystem of parachains, an easy
 //!   blockchain framework must exist. This is [Substrate](crate::polkadot_sdk::substrate),
 //!   [FRAME](crate::polkadot_sdk::frame_runtime) and [Cumulus](crate::polkadot_sdk::cumulus).

polkadot/roadmap/implementers-guide/src/node/backing/statement-distribution.md

@@ -22,7 +22,7 @@ in case of disputes. Any validator can be selected as the next relay-chain block
 advance for security reasons. As a result, all validators must have a up to date view of all possible parachain
 candidates + backing statements that could be placed on-chain in the next block.
 
-[This blog post](https://polkadot.com/blog/polkadot-v1-0-sharding-and-economic-security) puts it another way:
+[The wiki](https://wiki.polkadot.com/docs/learn-parachains-protocol) puts it another way:
 "Validators who aren't assigned to the parachain still listen for the attestations [statements] because whichever
 validator ends up being the author of the relay-chain block needs to bundle up attested parachain blocks for several
 parachains and place them into the relay-chain block."