Remove 'unstable' warning

content/application-service-api.md

@@ -4,8 +4,6 @@ weight: 30
 type: docs
 ---
 
-{{unstable\_warning\_block\_APPSERVICE\_RELEASE\_LABEL}}
-
 The Matrix client-server API and server-server APIs provide the means to
 implement a consistent self-contained federated messaging fabric.
 However, they provide limited means of implementing custom server-side

content/client-server-api/_index.md

@@ -4,8 +4,6 @@ weight: 10
 type: docs
 ---
 
-{{unstable\_warning\_block\_CLIENT\_RELEASE\_LABEL}}
-
 The client-server API provides a simple lightweight API to let clients
 send messages, control rooms and synchronise conversation history. It is
 designed to support both lightweight clients which store no state and

content/identity-service-api.md

@@ -4,8 +4,6 @@ weight: 40
 type: docs
 ---
 
-{{unstable\_warning\_block\_IDENTITY\_RELEASE\_LABEL}}
-
 The Matrix client-server and server-server APIs are largely expressed in
 Matrix user identifiers. From time to time, it is useful to refer to
 users by other ("third-party") identifiers, or "3PID"s, e.g. their email

content/push-gateway-api.md

@@ -4,8 +4,6 @@ weight: 50
 type: docs
 ---
 
-{{unstable\_warning\_block\_PUSH\_GATEWAY\_RELEASE\_LABEL}}
-
 Clients may want to receive push notifications when events are received
 at the homeserver. This is managed by a distinct entity called the Push
 Gateway.

content/server-server-api.md

@@ -4,8 +4,6 @@ weight: 20
 type: docs
 ---
 
-{{unstable\_warning\_block\_SERVER\_RELEASE\_LABEL}}
-
 Matrix homeservers use the Federation APIs (also known as server-server
 APIs) to communicate with each other. Homeservers use these APIs to push
 messages to each other in real-time, to retrieve historic messages from