Skip to content

Commit 5365440

Browse files
dreamorosiam29dleandrodamascena
authored
chore(docs): fix spelling issues (aws-powertools#3039)
Co-authored-by: Alexander Schueren <[email protected]> Co-authored-by: Leandro Damascena <[email protected]>
1 parent d63c912 commit 5365440

File tree

6 files changed

+8
-8
lines changed

6 files changed

+8
-8
lines changed

CONTRIBUTING.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -158,7 +158,7 @@ For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of
158158

159159
## Security issue notifications
160160

161-
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
161+
If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public GitHub issue.
162162

163163
## Licensing
164164

docs/core/logger.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -205,7 +205,7 @@ Use `POWERTOOLS_LOGGER_LOG_EVENT` environment variable to enable or disable (`tr
205205

206206
### Appending additional keys
207207

208-
You can append additional keys using either machanism:
208+
You can append additional keys using either mechanism:
209209

210210
* Add **extra keys** to a single log message by passing them to the log method directly
211211
* Append **temporary keys** to all future log messages via the `appendKeys()` method until `resetKeys()` is called

docs/upgrade.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -359,7 +359,7 @@ In v2, we have removed the `ContextExamples` from the `@aws-lambda-powertools/co
359359

360360
## Helper functions
361361

362-
We removed the deprecated `createLogger` and `createTracer` heper functions.
362+
We removed the deprecated `createLogger` and `createTracer` helper functions.
363363

364364
```typescript
365365
import { createLogger } from '@aws-lambda-powertools/logger';

docs/utilities/parameters.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -330,7 +330,7 @@ For example, if you have three parameters, _/param/a_, _/param/b_ and _/param/c_
330330

331331
If you use `transform` with `getMultiple()`, you might want to retrieve and transform parameters encoded in different formats.
332332

333-
You can do this with a single request by using `transform: 'auto'`. This will instruct any provider to to infer its type based on the suffix and transform it accordingly.
333+
You can do this with a single request by using `transform: 'auto'`. This will instruct any provider to infer its type based on the suffix and transform it accordingly.
334334

335335
???+ info
336336
`transform: 'auto'` feature is available across all providers, including the high level functions.

docs/utilities/parser.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -118,7 +118,7 @@ If you want to extend a schema and transform a JSON stringified payload to an ob
118118

119119
1. Extend built-in `AlbSchema` using JSONStringified function to transform your payload
120120

121-
=== "Alb exmaple payload"
121+
=== "ALB example payload"
122122

123123
```json hl_lines="26"
124124
--8<-- "examples/snippets/parser/exampleAlbPayload.json"
@@ -131,7 +131,7 @@ If you want to extend a schema and transform a JSON stringified payload to an ob
131131

132132
1. make sure to set your schema to the correct key in the JSON payload
133133

134-
=== "SQS exmaple payload"
134+
=== "SQS example payload"
135135

136136
```json hl_lines="6 28"
137137
--8<-- "examples/snippets/parser/exampleSqsPayload.json"
@@ -280,7 +280,7 @@ We recommend to use the types provided by the parser utility. If you encounter a
280280

281281
## Testing your code
282282

283-
When testing your handler with [**parser decorator**](#parse-events) you need to use double assetion to bypass TypeScript type checking in your tests.
283+
When testing your handler with [**parser decorator**](#parse-events) you need to use double assertion to bypass TypeScript type checking in your tests.
284284
This is useful when you want to test the handler for invalid payloads or when you want to test the error handling.
285285
If you are you use middy middleware, you don't need to do this.
286286

docs/we_made_this.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ Discover how easy it is to quickly “power-up” your Node.js Lambda functions
4747

4848
> **Author: [Eoin Shanaghy](https://twitter.com/eoins){target="_blank"} :material-twitter:**
4949
50-
This post shows how to use AWS Lambda Powertools to quickly build Well-Architected serverless applications.
50+
This post shows how to use Powertools for AWS Lambda to quickly build Well-Architected Serverless applications.
5151

5252
* [https://fourtheorem.com/aws-lambda-powertools/](https://fourtheorem.com/aws-lambda-powertools/){target="_blank"}
5353

0 commit comments

Comments
 (0)