diff --git a/api-reference/endpoint/ipfs/pin-file-to-ipfs.mdx b/api-reference/endpoint/ipfs/pin-file-to-ipfs.mdx index 4e23038..5f527a2 100644 --- a/api-reference/endpoint/ipfs/pin-file-to-ipfs.mdx +++ b/api-reference/endpoint/ipfs/pin-file-to-ipfs.mdx @@ -113,7 +113,7 @@ await uploadBase64("SGVsbG8gZnJvbSBQaW5hdGEhIDop"); -Folders can also be uploaded via the API by creating an array of files and mapping over them to add them to the form data. This is different then having a single `file` entry and having multiple files for that one entry, which does not work. +Folders can also be uploaded via the API by creating an array of files and mapping over them to add them to the form data. This is different than having a single `file` entry and having multiple files for that one entry, which does not work. diff --git a/files/uploading-files.mdx b/files/uploading-files.mdx index ab9f47a..b34a63f 100644 --- a/files/uploading-files.mdx +++ b/files/uploading-files.mdx @@ -369,7 +369,7 @@ The profile a file was uploaded with is returned as `cid_version` on the file's ### Client Side Uploads -There are situations where you may need to upload a file client side instead of server side. A great example is in Next.js where there is a 4MB file size restriction for files passed through Next's API routes. To solve this you can create a signed upload URL on the server and then pass it to the client for it to be consumed. This way your admin API key stays safe behind a server. Creating signed upload URLs can be done with either the [SDK](/sdk/upload/public/create-signed-url) or the [API](/api-reference/endpoint/create-signed-upload-url), and you can designate how long the URL is valid for or if there is other infromation you want to include such as metadata or a group ID. +There are situations where you may need to upload a file client side instead of server side. A great example is in Next.js where there is a 4MB file size restriction for files passed through Next's API routes. To solve this you can create a signed upload URL on the server and then pass it to the client for it to be consumed. This way your admin API key stays safe behind a server. Creating signed upload URLs can be done with either the [SDK](/sdk/upload/public/create-signed-url) or the [API](/api-reference/endpoint/create-signed-upload-url), and you can designate how long the URL is valid for or if there is other information you want to include such as metadata or a group ID. Setting up a server side API endpoint might look something like this: