title fix

hcourdent · hcourdent · commit aadbee24d8b8 · 2024-02-21T18:52:10.000+01:00
diff --git a/docs/core_concepts/11_persistent_storage/index.mdx b/docs/core_concepts/11_persistent_storage/index.mdx
@@ -252,7 +252,7 @@ Then from Windmill, just [fill the S3 resource type](../../integrations/s3.md).
 
 4. [Integrate it to Windmill](../../integrations/microsoft-azure-blob.md) by filling the [resource type details](https://hub.windmill.dev/resource_types/137) for Azure Blob APIs.
 
-### Connect your Windmill workspace to your S3 bucket or you Azure Blob storage
+### Connect your Windmill workspace to your S3 bucket or your Azure Blob storage
 
 Once you've created an [S3 or Azure Blob resource](../../integrations/s3.md) in Windmill, go to the workspace settings > S3 Storage. Select the resource and click Save.
 
diff --git a/docs/core_concepts/18_files_binary_data/index.mdx b/docs/core_concepts/18_files_binary_data/index.mdx
@@ -12,15 +12,15 @@ Binary data, such as files, are not easy to handle. Windmill provides two option
 
 ## Windmill integration with S3 or Azure Blob Storage
 
-The recommended way to store binary data is to upload it to S3 leveraging [Windmill's native S3 integrations](../11_persistent_storage/index.mdx#connect-your-windmill-workspace-to-your-s3-bucket-or-you-azure-blob-storage).
+The recommended way to store binary data is to upload it to S3 leveraging [Windmill's native S3 integrations](../11_persistent_storage/index.mdx#connect-your-windmill-workspace-to-your-s3-bucket-or-your-azure-blob-storage).
 
 :::info
 
 Windmill's integration with S3 and Azure Blob Storage works exactly the same and the features described below works in both cases. The only difference is that you need to select an `azure_blob` resource when setting up the S3 storage in the Workspace settings.
 
 :::
 
-By [setting a S3 resource for the workspace](../11_persistent_storage/index.mdx#connect-your-windmill-workspace-to-your-s3-bucket-or-you-azure-blob-storage), you can have an easy access to your bucket from the script editor. It becomes easy to consume S3 files as input, and write back to S3 anywhere in a script.
+By [setting a S3 resource for the workspace](../11_persistent_storage/index.mdx#connect-your-windmill-workspace-to-your-s3-bucket-or-your-azure-blob-storage), you can have an easy access to your bucket from the script editor. It becomes easy to consume S3 files as input, and write back to S3 anywhere in a script.
 
 S3 files in Windmill are just pointers to the S3 object using its key. As such, they are represented by a simple JSON:
 
@@ -45,8 +45,8 @@ Windmill provides helpers in its SDKs to consume and produce S3 file seamlessly.
 <div className="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
 		title="Persistent Storage - S3 Integration"
-		description="Connect your Windmill workspace to your S3 bucket or you Azure Blob storage."
-		href="/docs/core_concepts/persistent_storage#connect-your-windmill-workspace-to-your-s3-bucket-or-you-azure-blob-storage"
+		description="Connect your Windmill workspace to your S3 bucket or your Azure Blob storage."
+		href="/docs/core_concepts/persistent_storage#connect-your-windmill-workspace-to-your-s3-bucket-or-your-azure-blob-storage"
 	/>
 </div>
 
@@ -303,7 +303,7 @@ def main(input_file: S3Object):
 
 :::info
 
-Polars and DuckDB needs to be configured to access S3 within the Windmill script. The job will need to accessed the S3 resources, which either needs to be accessible to the user running the job, or the S3 resource needs to be [set as public in the workspace settings](/docs/core_concepts/persistent_storage#connect-your-windmill-workspace-to-your-s3-bucket-or-you-azure-blob-storage).
+Polars and DuckDB needs to be configured to access S3 within the Windmill script. The job will need to accessed the S3 resources, which either needs to be accessible to the user running the job, or the S3 resource needs to be [set as public in the workspace settings](/docs/core_concepts/persistent_storage#connect-your-windmill-workspace-to-your-s3-bucket-or-your-azure-blob-storage).
 
 :::
 
diff --git a/docs/core_concepts/27_data_pipelines/index.mdx b/docs/core_concepts/27_data_pipelines/index.mdx
@@ -72,8 +72,8 @@ More details on S3 integration:
 <div className="grid grid-cols-2 gap-6 mb-4">
 	<DocCard
 		title="Persistent Storage - S3 Integration"
-		description="Connect your Windmill workspace to your S3 bucket or you Azure Blob storage."
-		href="/docs/core_concepts/persistent_storage#connect-your-windmill-workspace-to-your-s3-bucket-or-you-azure-blob-storage"
+		description="Connect your Windmill workspace to your S3 bucket or your Azure Blob storage."
+		href="/docs/core_concepts/persistent_storage#connect-your-windmill-workspace-to-your-s3-bucket-or-your-azure-blob-storage"
 	/>
 </div>
 
