Apply suggestions from code review

Author: Oxyjun

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

@@ -76,7 +76,7 @@ Generate a presigned URL by referring to the following examples:
 
 ### Example of generating presigned URLs
 
-A possible use case may be restricting an application to only be able to upload to a specific URL. With presigned URLs, your central signing application might look like the following JavaScript code running on Cloudflare Workers, workerd, or another platform (you might have to update the code based on the platform you are using).
+A possible use case may be restricting an application to only be able to upload to a specific URL. With presigned URLs, your central signing application might look like the following JavaScript code running on Cloudflare Workers, `workerd`, or another platform (you might have to update the code based on the platform you are using).
 
 If the application received a request for `https://example.com/uploads/dog.png`, it would respond with a presigned URL allowing a user to upload to your R2 bucket at the `/uploads/dog.png` path.
 
@@ -140,11 +140,16 @@ export default {
 
 ## Differences between presigned URLs and R2 binding
 
-When using the 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 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.
 
-However, when using presigned URLs, you will need to create and use the token secrets in your Worker code.
+- When using presigned URLs, you will need to create and use the token secrets in your Worker code.
 
-In some cases, Workers lets 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, you would need to sign specific headers and require the sender to send the same headers. You can modify the previous example to sign additional headers:
+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:
+
+ - 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.
+ 
+ You can modify the previous example to sign additional headers:
 
 ```ts
 const signed = await client.sign(