Small fix

Author: Oxyjun

src/content/docs/r2/api/s3/presigned-urls.mdx

@@ -145,7 +145,7 @@ export default {
 - When using an R2 binding, you will not need any token secrets in your Worker code. Instead, in your [Wrangler configuration file](/workers/wrangler/configuration/), you will create a [binding](/r2/api/workers/workers-api-usage/#3-bind-your-bucket-to-a-worker) to your R2 bucket. Additionally, authorization is handled in-line, which can reduce latency.
 - When using presigned URLs, you will need to create and use the token secrets in your Worker code.
 
-In some cases, R2 bindings let you implement certain functionality more easily. For example, if you wanted to offer a write-once guarantee so that users can only upload to a path once, with pre-signed URLs:
+In some cases, R2 bindings let you implement certain functionality more easily. For example, if you wanted to offer a write-once guarantee so that users can only upload to a path once:
 
 - With R2 binding: You only need to pass the parameter once.
 - With presigned URLs: You need to sign specific headers and require the sender to send the same headers.