diff --git a/docs/presets/remote-sources.mdx b/docs/presets/remote-sources.mdx
index 1169bf90ab..676972e453 100644
--- a/docs/presets/remote-sources.mdx
+++ b/docs/presets/remote-sources.mdx
@@ -128,9 +128,8 @@ fine.
 
 #### `companionCookiesRule`
 
-This option correlates to the [`Request.credentials` value][], which tells the
-plugin whether to send cookies to [Companion](/docs/companion) (`string`,
-default: `same-origin`).
+This option correlates to the [`Request.credentials` value][], which tells the plugin
+whether to send cookies to [Companion](/docs/companion) (`string`, default: `same-origin`).
 
 #### `target`
 
diff --git a/docs/uploader/aws-s3-multipart.mdx b/docs/uploader/aws-s3-multipart.mdx
index a21183ac72..106cbeeedd 100644
--- a/docs/uploader/aws-s3-multipart.mdx
+++ b/docs/uploader/aws-s3-multipart.mdx
@@ -34,10 +34,9 @@ it uploads a single object as a set of parts. This has certain benefits, such as
 improved throughput (uploading parts in parallel) and quick recovery from
 network issues (only the failed parts need to be retried). The downside is
 request overhead, as it needs to do creation, signing (unless you are [signing
-on the client][]), and completion requests besides the upload requests. For
-example, if you are uploading files that are only a couple kilobytes with a
-100ms roundtrip latency, you are spending 400ms on overhead and only a few
-milliseconds on uploading.
+on the client][]), and completion requests besides the upload requests. For example,
+if you are uploading files that are only a couple kilobytes with a 100ms roundtrip
+latency, you are spending 400ms on overhead and only a few milliseconds on uploading.
 
 **In short**
 
diff --git a/docs/uploader/tus.mdx b/docs/uploader/tus.mdx
index 15270ba6d7..9c3abf39fd 100644
--- a/docs/uploader/tus.mdx
+++ b/docs/uploader/tus.mdx
@@ -119,8 +119,8 @@ const headers = {
 ```
 
 Header values can also be derived from file data by providing a function. The
-function receives an [Uppy file][] and must return an object where the keys are
-header names, and values are header values.
+function receives an [Uppy file][] and must return an object where the keys are header
+names, and values are header values.
 
 ```js
 const headers = (file) => {
diff --git a/docs/uploader/xhr.mdx b/docs/uploader/xhr.mdx
index a38f29f875..8eaf5f28e2 100644
--- a/docs/uploader/xhr.mdx
+++ b/docs/uploader/xhr.mdx
@@ -130,8 +130,8 @@ const headers = {
 ```
 
 Header values can also be derived from file data by providing a function. The
-function receives an [Uppy file][] and must return an object where the keys are
-header names, and values are header values.
+function receives an [Uppy file][] and must return an object where the keys are header
+names, and values are header values.
 
 ```js
 const headers = (file) => {
diff --git a/yarn.lock b/yarn.lock
index abdeec9187..fed12c2451 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -26299,11 +26299,11 @@ __metadata:
   linkType: hard
 
 "prettier@npm:^3.0.3":
-  version: 3.2.5
-  resolution: "prettier@npm:3.2.5"
+  version: 3.3.2
+  resolution: "prettier@npm:3.3.2"
   bin:
     prettier: bin/prettier.cjs
-  checksum: 10/d509f9da0b70e8cacc561a1911c0d99ec75117faed27b95cc8534cb2349667dee6351b0ca83fa9d5703f14127faa52b798de40f5705f02d843da133fc3aa416a
+  checksum: 10/83214e154afa5aa9b664c2506640212323eb1376b13379b2413dc351b7de0687629dca3f00ff2ec895ebd7e3a2adb7d7e231b6c77606e2358137f2150807405b
   languageName: node
   linkType: hard