Merge pull request #64 from dyte-in/fix-trailing-slash

fix: trailing slash config and paths changed

Author: vaibhavshn

android_versioned_docs/version-0.1.x/quickstart.mdx

@@ -7,7 +7,7 @@ sidebar_position: 2
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api/)), and pass them to Dyte's client SDK.
+Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api)), and pass them to Dyte's client SDK.
 
 There are 2 ways to launch a meeting:
 

android_versioned_docs/version-0.12.x/quickstart.mdx

@@ -7,7 +7,7 @@ sidebar_position: 2
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
 
-Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api/)), and pass them to Dyte's client SDK.
+Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api)), and pass them to Dyte's client SDK.
 
 There are 2 ways to launch a meeting:
 

android_versioned_docs/version-0.14.x/quickstart.mdx

@@ -7,7 +7,7 @@ sidebar_position: 2
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
 
-Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api/)), and pass them to Dyte's client SDK.
+Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api)), and pass them to Dyte's client SDK.
 
 There are 2 ways to launch a meeting:
 

android_versioned_docs/version-0.2.x/quickstart.mdx

@@ -7,7 +7,7 @@ sidebar_position: 2
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
 
-Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api/)), and pass them to Dyte's client SDK.
+Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api)), and pass them to Dyte's client SDK.
 
 There are 2 ways to launch a meeting:
 

android_versioned_docs/version-0.6.x/quickstart.mdx

@@ -7,7 +7,7 @@ sidebar_position: 2
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
 
-Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api/)), and pass them to Dyte's client SDK.
+Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api)), and pass them to Dyte's client SDK.
 
 There are 2 ways to launch a meeting:
 

android_versioned_docs/version-0.7.x/quickstart.mdx

@@ -7,7 +7,7 @@ sidebar_position: 2
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
 
-Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api/)), and pass them to Dyte's client SDK.
+Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api)), and pass them to Dyte's client SDK.
 
 There are 2 ways to launch a meeting:
 

docs/android/quickstart.mdx

@@ -7,7 +7,7 @@ sidebar_position: 2
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
 
-Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api/)), and pass them to Dyte's client SDK.
+Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api)), and pass them to Dyte's client SDK.
 
 There are 2 ways to launch a meeting:
 

docs/flutter/quickstart.mdx

@@ -7,7 +7,7 @@ sidebar_position: 2
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
 
-Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api/)), and pass them to Dyte's `DyteMeeting` widget.
+Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api)), and pass them to Dyte's `DyteMeeting` widget.
 
 1. Import the package.
 

docs/guides/controlling-an-active-session.mdx

@@ -1,5 +1,5 @@
 # Controlling an Active Session
-An active session (ongoing meeting) can be controlled programatically using [Active Session APIs](/api/v2/#/operations/GetActiveSession). For now, you can do following things in an Active Session.
+An active session (ongoing meeting) can be controlled programatically using [Active Session APIs](/api/v2#operations/GetActiveSession). For now, you can do following things in an Active Session.
 * Fetch active session details.
 * Kick one or more participants.
 * Kick all participants.
@@ -8,25 +8,25 @@ An active session (ongoing meeting) can be controlled programatically using [Act
 * Create a poll.
 
 ## Get Active Session details
-You can get an active session of a meeting using `meetingId`. Refer to [`GET` active session endpoint](/api/v2/#/operations/GetActiveSession) under [v2 API Reference](/api/v2/#/).
+You can get an active session of a meeting using `meetingId`. Refer to [`GET` active session endpoint](/api/v2#operations/GetActiveSession) under [v2 API Reference](/api/v2#).
 
 ## Kick one or more participants
 You can kick one or multiple participants from an active session using `participant_ids` or `custom_participant_ids`.
 
 > `custom_participant_id` is called `clientSpecificId` in v1 and it's the same id that you pass in body of [Add Participant Endpoint](/api/#/operations/addParticipant)
 
-Refer to [Kick Participant endpoint](/api/v2/#/operations/KickPartcipants) to see complete details.
+Refer to [Kick Participant endpoint](/api/v2#operations/KickPartcipants) to see complete details.
 
 ## Kick all participants
-All participants can be kicked out from an active session using [Kick all endpoint](/api/v2/#/operations/KickAllParticipants)
+All participants can be kicked out from an active session using [Kick all endpoint](/api/v2#operations/KickAllParticipants)
 
 ## Mute one or more participants
-Similar to kicking participants, one or multiple participants can be muted in an active session using `participant_ids` or `custom_participant_ids`. Refer to [Mute participants endpoint](/api/v2/#/operations/MuteParticipants) to see request body and response.
+Similar to kicking participants, one or multiple participants can be muted in an active session using `participant_ids` or `custom_participant_ids`. Refer to [Mute participants endpoint](/api/v2#operations/MuteParticipants) to see request body and response.
 
 ## Mute all participants
-All participants can be muted in an active session using [Mute all endpoint](/api/v2/#/operations/MuteAllParticipants). You can also specify if participants can unmute themselves or not using `allow_unmute` option in request body. Refer to [Mute all endpoint](/api/v2/#/operations/MuteAllParticipants) to see complete details.
+All participants can be muted in an active session using [Mute all endpoint](/api/v2#operations/MuteAllParticipants). You can also specify if participants can unmute themselves or not using `allow_unmute` option in request body. Refer to [Mute all endpoint](/api/v2#operations/MuteAllParticipants) to see complete details.
 
 ## Create a poll
-You can also create a poll in an active session programatically. Poll will always be created under your organization's name. You can specify different options while creating poll like `hide_votes`, `anonymous` etc. Refer to [Create Poll endpoint](/api/v2/#/operations/CreatePoll) to see complete details.
+You can also create a poll in an active session programatically. Poll will always be created under your organization's name. You can specify different options while creating poll like `hide_votes`, `anonymous` etc. Refer to [Create Poll endpoint](/api/v2#operations/CreatePoll) to see complete details.
 
 You can see list of all endpoints for active session in `activesession` section under [v2 API Reference](/api/v2).

docs/ios/quickstart.mdx

@@ -7,7 +7,7 @@ sidebar_position: 2
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api/)), and pass them to Dyte's client SDK.
+Get the `roomName` for the meeting and the participant's `authToken` from our backend APIs (read more about our server APIs [here](/api)), and pass them to Dyte's client SDK.
 
 There are 2 ways to manage a meeting view: