Update 1.13 release status (#261)

* docs: update 1.13 release status (Migrate page)

* docs: update 1.13 release status (Settings page)

Author: Luckz

en/Plugins/Guides/Migrate to declarative settings.md

@@ -8,7 +8,7 @@ As of Obsidian 1.13.0, plugin settings tabs can be defined declaratively by over
 This guide walks through converting an existing imperative `display()` tab to the new API.
 
 > [!important] Requires Obsidian 1.13.0+
-> The declarative settings API described on this page (`getSettingDefinitions()`) requires Obsidian 1.13.0, which is currently in an insider build. If you need to support older Obsidian versions, see [[#Path B: dual support]].
+> The declarative settings API described on this page (`getSettingDefinitions()`) requires Obsidian 1.13.0. If you need to support older Obsidian versions, see [[#Path B: dual support]].
 
 ## What you'll learn
 

en/Plugins/User interface/Settings.md

@@ -5,7 +5,7 @@ In this guide, you'll learn how you can create a settings page like this 👇
 ![[settings.png]]
 
 > [!important] Requires Obsidian 1.13.0+
-> The declarative settings API documented on this page (`getSettingDefinitions()`) requires Obsidian 1.13.0, which is currently in an insider build. If you need to support older Obsidian versions, see [[Migrate to declarative settings#Path B: dual support|the dual-support pattern]]. For the pre-1.13 imperative approach, jump to [[#Legacy: imperative display() approach]].
+> The declarative settings API documented on this page (`getSettingDefinitions()`) requires Obsidian 1.13.0. If you need to support older Obsidian versions, see [[Migrate to declarative settings#Path B: dual support|the dual-support pattern]]. For the pre-1.13 imperative approach, jump to [[#Legacy: imperative display() approach]].
 
 The main reason to add settings to a plugin is to store configuration that persists even after the user quits Obsidian. The following example demonstrates how to save and load settings from disk: