Skip to content

Commit d81ddcc

Browse files
authored
docs: fix typos (#74)
1 parent b729127 commit d81ddcc

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ When calling `open-next build`, OpenNext **runs `next build`** to build the Next
7373

7474
#### Building the Next.js app
7575

76-
OpenNext runs the `build` script in your `package.json` file. Depnding on the lock file found in the app, the corresponding packager manager will be used. Either `npm run build`, `yarn build`, or `pnpm build` will be run.
76+
OpenNext runs the `build` script in your `package.json` file. Depending on the lock file found in the app, the corresponding packager manager will be used. Either `npm run build`, `yarn build`, or `pnpm build` will be run.
7777

7878
#### Transforming the build output
7979

@@ -117,7 +117,7 @@ public,max-age=0,s-maxage=31536000,must-revalidate
117117

118118
Create a Lambda function using the code in the `.open-next/image-optimization-function` folder, with the handler `index.mjs`. Ensure that the **arm64** architecture is used.
119119

120-
This function handles image optimization requests when the Next.js `<Image>` component is used. The [sharp](https://www.npmjs.com/package/sharp) library, which is bundled with the function, is used to convert the image. The library is compiled against the `arm64` architecture and is intended to run on AWS Lamba Arm/Graviton2 architecture. [Learn about the better cost-performance offered by AWS Graviton2 processors.](https://aws.amazon.com/blogs/aws/aws-lambda-functions-powered-by-aws-graviton2-processor-run-your-functions-on-arm-and-get-up-to-34-better-price-performance/)
120+
This function handles image optimization requests when the Next.js `<Image>` component is used. The [sharp](https://www.npmjs.com/package/sharp) library, which is bundled with the function, is used to convert the image. The library is compiled against the `arm64` architecture and is intended to run on AWS Lambda Arm/Graviton2 architecture. [Learn about the better cost-performance offered by AWS Graviton2 processors.](https://aws.amazon.com/blogs/aws/aws-lambda-functions-powered-by-aws-graviton2-processor-run-your-functions-on-arm-and-get-up-to-34-better-price-performance/)
121121

122122
Note that the image optimization function responds with the `Cache-Control` header, so the image will be cached both at the CDN level and at the browser level.
123123

@@ -296,7 +296,7 @@ This does a few things:
296296
It is recommended to **turn off debug mode when building for production** because:
297297

298298
1. Un-minified function code is 2-3X larger than minified code. This will result in longer Lambda cold start times.
299-
1. Logging the event object on each request can result in a lot of logs being written to AWS CloudWatch. This will result in increated AWS costs.
299+
1. Logging the event object on each request can result in a lot of logs being written to AWS CloudWatch. This will result in increased AWS costs.
300300

301301
## Opening an issue
302302

@@ -342,7 +342,7 @@ We previously built the app using the "minimalMode" and having the same architec
342342

343343
#### How does OpenNext compared to AWS Amplify?
344344

345-
OpenNext is an open source initiative, and there are a couple of advantages when comapred to Amplify:
345+
OpenNext is an open source initiative, and there are a couple of advantages when compared to Amplify:
346346

347347
1. The community contributions to OpenNext allows it to have better feature support.
348348

0 commit comments

Comments
 (0)