diff --git a/concepts/topics.mdx b/concepts/topics.mdx
index cc533a8b..ab5eb6e6 100644
--- a/concepts/topics.mdx
+++ b/concepts/topics.mdx
@@ -13,7 +13,7 @@ Users can also assign a name to a topic. This name doesn't need to be unique and
A topic would get assigned different subscribers that will receive a notification every time a notification is sent to the topic.
-## Create A Topic
+## Create a topic
In order to be able to send a notification to a topic, first the user needs to create one. It can be done like this:
@@ -42,7 +42,7 @@ const key = "unique-topic-identifier";
const result = await novu.topics.get(key);
```
-## Rename a Topic
+## Rename a topic
Descriptive name given during creation of topic can be changed later. This can be done like this:
@@ -61,7 +61,7 @@ This will return the whole Topic information, including the subscribers if havin
Topic Key can not be changed
-## Add subscribers to a Topic
+## Add subscribers to a topic
Adding subscribers to the topic is the main usecase of topic. A topic is like a group of subscribers. A notification can be sent to all subscribers of a topic at once
@@ -98,6 +98,8 @@ This call will return a response in the shape of:
The field `succeeded` will return the array of subscriber ids that have been correctly assigned to the topic. The field `failed` will show up only if there has been any subscriber that couldn't been assigned to the topic. This probably will happen if there is any typo in the given subscriberId or if the given subscriberId doesn't belong to the environment and the organization where the topic has been created.
+One topic can have maximum 500K subscribers
+
### Create topic on the fly
To facilitate flows we allow to create a topic on the fly when adding subscribers.
@@ -130,7 +132,7 @@ const response = await novu.topics.getSubscriber(
without making extra calls to Novu.
-## Remove a subscriber from a Topic
+## Remove a subscriber from a topic
A single or group of subscribers can be removed from an existing topic.
diff --git a/inbox/react/get-started.mdx b/inbox/react/get-started.mdx
index ce15a622..45526937 100644
--- a/inbox/react/get-started.mdx
+++ b/inbox/react/get-started.mdx
@@ -53,24 +53,6 @@ Possible reasons for the Inbox not loading properly:
-
-
-The Inbox should be wrapped in ``
-
-
-
-
-
-The redirect URL is for the entire notification item, When the user clicks the notification, the user will be routed to that url. CTA are two call-to-action buttons. `onNotificationClick` function prop is used for redirecting url and the `onActionClick` function prop is used for CTA.
-
-
-
-
-
-Bell icon and Inbox in Novu dashboard is only for receiving system related notifications like user you invited has joined, password reset request sent. It can not to used to test Inbox. Consider using our [codesandbox example](https://codesandbox.io/s/kind-nova-xv6s9g?fontsize=14&hidenavigation=1&theme=dark) instead.
-
-
-
Our Inbox is configures for all hosts. Please disable root level `withCredentials` config in axios or fetch http requests.
diff --git a/inbox/react/multiple-tabs.mdx b/inbox/react/multiple-tabs.mdx
index 0760b683..21b50d4a 100644
--- a/inbox/react/multiple-tabs.mdx
+++ b/inbox/react/multiple-tabs.mdx
@@ -47,3 +47,5 @@ function Novu() {
+
+Here tab value is taken from workflow tags. Tags can be configured in options field of [workflow](/sdks/framework/typescript/workflow).