Thanks to visit codestin.com
Credit goes to github.com

Skip to content
This repository was archived by the owner on May 13, 2024. It is now read-only.

Commit f84d34d

Browse files
committed
Update Single Pages “intro”
1 parent 9edb1ea commit f84d34d

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

docs/intro.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,11 @@ draft: false
55
sidebar_label: Introduction
66
sidebar_position: 0
77
keywords:
8-
- deriv-api
9-
- getting-started-deriv-api
10-
description: how to use deriv api, deriv api gettting started
8+
- deriv
9+
- api
10+
- getting
11+
- started
12+
description: Getting started with Deriv API
1113
---
1214

1315
Our Documentation is divided in several sections:
@@ -22,17 +24,15 @@ Our Documentation is divided in several sections:
2224

2325
### Quick Start
2426

25-
# Introduction
27+
Have a look at the [Core Concept](category/core-concepts) and [Terminology](category/terminology) pages and take your time to read through it. These concepts will help you get familiar with our websocket server api and how to use it more efficiently. They are not related to any of our frameworks or libraries.
2628

27-
Please skim through our [Core Concept](category/core-concepts) and [Terminology](category/terminology) pages, these pages will help you get familiar with our `websocket server api` features, the concepts introduced in these pages are not related to any of our frameworks or libraries, so in order to use our `websocket server api` in an efficient way it's better if you grasp all the information provided there.
28-
29-
When you're done with [Core Concept](category/core-concepts) and [Terminology](category/terminology) pages you can choose your implementation approach based on the language / framework / library you want to work with in your application.
29+
When you read through the [Core Concept](category/core-concepts) and [Terminology](category/terminology) pages, you can start choosing your implementation approach based on the language / framework / library you want to use in your application.
3030

3131
Using our [Client Libraries](category/client-libraries) is optional and you can get the same result with the tutorials provided in [Languages Section](category/languages) as well, but our client libraries provide more `robust`, `type safe` API calls for you.
3232

3333
### Using our websocket server with just languages features
3434

35-
If you want to use our `websocket server` with pure languages feature of your choice please check out [Languages Section](category/languages) and continue your journey from there.
35+
If you want to use our websocket server api with a specific coding language, then have a look at the [Languages Section](category/languages) Section and continue your journey from there.
3636

3737
:::caution
3838
We suggest using our [Client Libraries](category/client-libraries), since they give you better developer experience.

0 commit comments

Comments
 (0)