[incubator-devlake-website] branch main updated: Update Glossary.md

[zk...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

zky pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git


The following commit(s) were added to refs/heads/main by this push:
     new 8f61a3cb Update Glossary.md
8f61a3cb is described below

commit 8f61a3cb2f63457c71e1d38cdd3fcd5536b00dcd
Author: Bishal Das <70...@users.noreply.github.com>
AuthorDate: Mon Aug 8 20:16:26 2022 +0530

    Update Glossary.md
---
 docs/Glossary.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/Glossary.md b/docs/Glossary.md
index dc1a046d..6d516b9f 100644
--- a/docs/Glossary.md
+++ b/docs/Glossary.md
@@ -42,7 +42,7 @@ DevLake normally uses one [data plugin](Glossary.md#data-plugins) to pull data f
 You can set up a new data connection either during the first step of creating a blueprint, or in the Connections page that can be accessed from the navigation bar. Because one single data connection can be reused in multiple blueprints, you can update the information of a particular data connection in Connections, to ensure all its associated blueprints will run properly. For example, you may want to update your GitHub token in a data connection if it goes expired.
 
 ### Data Scope
-**In a blueprint, each data connection can have multiple sets of data scope configurations, including GitHub or GitLab projects, Jira boards and their corresponding[data entities](Glossary.md#data-entities).** The fields for data scope configuration vary according to different data sources.
+**In a blueprint, each data connection can have multiple sets of data scope configurations, including GitHub or GitLab projects, Jira boards and their corresponding [data entities](Glossary.md#data-entities).** The fields for data scope configuration vary according to different data sources.
 
 Each set of data scope refers to one GitHub or GitLab project, or one Jira board and the data entities you would like to sync for them, for the convenience of applying transformation in the next step. For instance, if you wish to sync 5 GitHub projects, you will have 5 sets of data scope for GitHub.