Skip to content

Commit

Permalink
docs(lambda-go): fix typos (aws#29567)
Browse files Browse the repository at this point in the history
### Issue # (if applicable)

### Reason for this change
Typos in doc

### Description of changes

### Description of how you validated changes

### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
  • Loading branch information
matthiasgubler authored and jun1-t committed Mar 23, 2024
1 parent 1f51866 commit 97cfc4d
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions packages/@aws-cdk/aws-lambda-go-alpha/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,15 +29,15 @@ Define a `GoFunction`:

```ts
new go.GoFunction(this, 'handler', {
entry: 'app/cmd/api',
entry: 'lambda-app/cmd/api',
});
```

By default, if `entry` points to a directory, then the construct will assume there is a Go entry file (i.e. `main.go`).
Let's look at an example Go project:

```bash
lamda-app
lambda-app
├── cmd
│   └── api
│   └── main.go
Expand Down Expand Up @@ -244,7 +244,7 @@ all of your functions if anything changes, then `AssetHashType.SOURCE` will prob
For example, if my app looked like this:

```bash
lamda-app
lambda-app
├── cmd
│   └── api
│   └── main.go
Expand All @@ -263,7 +263,7 @@ should trigger a new deploy, I could specify `AssetHashType.SOURCE`.
On the other hand, if I had a project that deployed multiple Lambda functions, for example:

```bash
lamda-app
lambda-app
├── cmd
│   ├── api
│   │   └── main.go
Expand Down

0 comments on commit 97cfc4d

Please sign in to comment.