Merge pull request #291331 from whhender/patch-574747

Clarifying file typing

Author: prmerger-automator[bot]

articles/synapse-analytics/spark/apache-spark-manage-workspace-packages.md

@@ -4,7 +4,7 @@ description: Learn how to add and manage libraries to workspace in Azure Synapse
 author: shuaijunye
 ms.service: azure-synapse-analytics
 ms.topic: conceptual
-ms.date: 11/03/2022
+ms.date: 12/03/2024
 ms.author: shuaijunye
 ms.subservice: spark
 ---
@@ -15,8 +15,8 @@ Workspace packages can be custom or private wheel (Python), jar (Scala/Java), or
 
 To add workspace packages:
 1. Navigate to the **Manage** > **Workspace packages** tab.
-2. Upload your wheel files by using the file selector.
-3. Once the files have been uploaded to the Azure Synapse workspace, you can add these packages to a given Apache Spark pool.
+2. Upload your files using the file selector.
+3. Once the files have been uploaded to the Azure Synapse workspace, you can add these packages to an Apache Spark pool.
 
   :::image type="content" source="./media/apache-spark-azure-portal-add-libraries/studio-add-workspace-package.png" alt-text="Screenshot that highlights workspace packages." lightbox="./media/apache-spark-azure-portal-add-libraries/studio-add-workspace-package.png":::
 
@@ -26,10 +26,10 @@ To add workspace packages:
 >- Once Workspace Packages are used to install packages on a given Apache Spark pool, there is a limitation that you can no longer specify packages using the Storage account path on the same pool.  
 
 > [!NOTE]
-> It's recommended that you don't have multiple wheel packages with the same name in a workspace. If you want to use a different version of the same wheel package, you have to delete the existing version and upload the new one.
+> It's recommended that you don't have multiple packages with the same name in a workspace. If you want to use a different version of the same package, you have to delete the existing version and upload the new one.
 
 ## Storage account
-Custom-built wheel packages can be installed on the Apache Spark pool by uploading all the wheel files into the Azure Data Lake Storage (Gen2) account that is linked with the Synapse workspace. 
+Custom-built packages can be installed on the Apache Spark pool by uploading all the files into the Azure Data Lake Storage (Gen2) account that is linked with the Synapse workspace. 
 
 The files should be uploaded to the following path in the storage account's default container: 
 
@@ -39,7 +39,7 @@ abfss://<file_system>@<account_name>.dfs.core.windows.net/synapse/workspaces/<wo
 
 >[!WARNING]
 > - In some cases, you may need to create the file path based on the structure above if it does not already exist. For example, you may need to add the ```python``` folder within the ```libraries``` folder if it does not already exist.
-> - This method of managing custom wheel files will not be supported on the Azure Synapse Runtime for Apache Spark 3.0. Please refer to the Workspace packages feature to manage custom wheel files.
+> - This method of managing custom files will not be supported on the Azure Synapse Runtime for Apache Spark 3.0. Please refer to the Workspace packages feature to manage custom files.
 
 > [!IMPORTANT]
 > To install custom libraries using the Azure DataLake Storage method, you must have the **Storage Blob Data Contributor** or **Storage Blob Data Owner** permissions on the primary Gen2 Storage account that is linked to the Azure Synapse Analytics workspace.