chore: add beta labels

BuildOnBeam · May 30, 2024 · af572bc · af572bc
1 parent 4b4a93e
commit af572bc
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 5 deletions.
diff --git a/pages/service/_meta.json b/pages/service/_meta.json
@@ -8,10 +8,10 @@
     "title": "Getting started"
   },
   "operations": {
-    "title": "Operations"
+    "title": "Operations (beta)"
   },
   "sessions": {
-    "title": "Sessions"
+    "title": "Sessions (beta)"
   },
   "--- Guides": {
     "type": "separator",

diff --git a/pages/service/operations/introduction.mdx b/pages/service/operations/introduction.mdx
@@ -2,7 +2,7 @@
 title: Operations
 ---
 
-# Introduction to Operations
+# Introduction to Operations (beta)
 
 Operations are the cornerstone of the self-custodial service in Beam. They facilitate the interaction between you and the end-user, who needs to sign for transactions.
 

diff --git a/pages/service/self-custody/introduction.mdx b/pages/service/self-custody/introduction.mdx
@@ -2,7 +2,7 @@
 title: Self-custody
 ---
 
-# Introduction to self-custody
+# Introduction to self-custody (beta)
 
 Through our new self-custody implementation, you are able to set-up self-custodial users with Beam. The implementation is a new service that works based on self-custodial private keys, and newly deployed account abstractions. Existing Profiles that you created, won't be available in this new service.
 

diff --git a/pages/service/sessions/introduction.mdx b/pages/service/sessions/introduction.mdx
@@ -2,7 +2,7 @@
 title: Sessions
 ---
 
-# Introduction to Sessions
+# Introduction to Sessions (beta)
 
 A self-custody implementation for your users means that the ownership of the account abstraction used, is **owned** by the private key in control of the user. Every time you want to interact with the blockchain on the users' behalf, you will need to ask them to sign a transaction.