Fix doc: start_destroy doesn't need asset to be frozen (paritytech#5204)

Fix paritytech#5184

`owner` can set himself as a `freezer` and freeze the asset so
requirement is not really needed. And requirement is not implemented.

---------

Co-authored-by: Bastian Köcher <git@kchr.de>
Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>

prdoc/pr_5204.prdoc

@@ -0,0 +1,13 @@
+title: "Pallet assets: fix doc: start_destroy never required asset to be frozen"
+
+doc:
+  - audience: Runtime Dev
+    description: |
+      In pallet assets calling `start_destroy` doesn't require the asset to be frozen. Doc is fixed.
+
+
+crates:
+  - name: pallet-assets
+    bump: patch
+  - name: frame-support
+    bump: patch

substrate/frame/assets/src/lib.rs

@@ -801,8 +801,6 @@ pub mod pallet {
 		///
 		/// - `id`: The identifier of the asset to be destroyed. This must identify an existing
 		///   asset.
-		///
-		/// The asset class must be frozen before calling `start_destroy`.
 		#[pallet::call_index(2)]
 		pub fn start_destroy(origin: OriginFor<T>, id: T::AssetIdParameter) -> DispatchResult {
 			let maybe_check_owner = match T::ForceOrigin::try_origin(origin) {

substrate/frame/support/src/traits/tokens/misc.rs

@@ -98,7 +98,7 @@ pub enum WithdrawConsequence<Balance> {
 	/// There has been an overflow in the system. This is indicative of a corrupt state and
 	/// likely unrecoverable.
 	Overflow,
-	/// Not enough of the funds in the account are unavailable for withdrawal.
+	/// Not enough of the funds in the account are available for withdrawal.
 	Frozen,
 	/// Account balance would reduce to zero, potentially destroying it. The parameter is the
 	/// amount of balance which is destroyed.