Merge pull request #221634 from jonburchel/patch-34

Update concepts-linked-services.md

Author: prmerger-automator[bot]

articles/data-factory/concepts-linked-services.md

@@ -28,7 +28,7 @@ To learn more read the introductory article for [Azure Data Factory](introductio
 
 Azure Data Factory and Azure Synapse Analytics can have one or more pipelines. A **pipeline** is a logical grouping of **activities** that together perform a task. The activities in a pipeline define actions to perform on your data. For example, you might use a copy activity to copy data from SQL Server to Azure Blob storage. Then, you might use a Hive activity that runs a Hive script on an Azure HDInsight cluster to process data from Blob storage to produce output data. Finally, you might use a second copy activity to copy the output data to Azure Synapse Analytics, on top of which business intelligence (BI) reporting solutions are built. For more information about pipelines and activities, see [Pipelines and activities](concepts-pipelines-activities.md).
 
-Now, a **dataset** is a named view of data that simply points or references the data you want to use in your **activities** as inputs and outputs.
+Now, a **dataset** is a named view of data that simply points to or references the data you want to use in your **activities** as inputs and outputs.
 
 Before you create a dataset, you must create a **linked service** to link your data store to the Data Factory or Synapse Workspace. Linked services are much like connection strings, which define the connection information needed for the service to connect to external resources. Think of it this way; the dataset represents the structure of the data within the linked data stores, and the linked service defines the connection to the data source. For example, an Azure Storage linked service links a storage account to the service. An Azure Blob dataset represents the blob container and the folder within that Azure Storage account that contains the input blobs to be processed.