Fixing README

README.md

@@ -1,7 +1,5 @@
 [//]: # (This file was autogenerated using `zio-sbt-website` plugin via `sbt generateReadme` command.)
-
 [//]: # (So please do not edit it manually. Instead, change "docs/index.md" file or sbt setting keys)
-
 [//]: # (e.g. "readmeDocumentation" and "readmeSupport".)
 
 # ZIO Lambda
@@ -14,11 +12,11 @@ A ZIO-based AWS Custom Runtime compatible with GraalVM Native Image.
 
 ```scala
 libraryDependencies += "dev.zio" %% "zio-json" % "0.6.2"
-libraryDependencies += "dev.zio" %% "zio-lambda" % "1.0.4"
+libraryDependencies += "dev.zio" %% "zio-lambda" % "1.0.5"
 
 // Optional dependencies
-libraryDependencies += "dev.zio" %% "zio-lambda-event" % "1.0.4"
-libraryDependencies += "dev.zio" %% "zio-lambda-response" % "1.0.4"
+libraryDependencies += "dev.zio" %% "zio-lambda-event"    % "1.0.5"
+libraryDependencies += "dev.zio" %% "zio-lambda-response" % "1.0.5"
 ```
 
 ## Usage
@@ -39,12 +37,9 @@ object SimpleHandler extends ZIOAppDefault {
    override val run =
       ZLambdaRunner.serve(app)
 }
-
 ```
 
-zio-lambda depends on [**zio-json**](https://github.com/zio/zio-json) for decoding any event you send to it and
-enconding any response you send back to the Lambda service. You can either create your own data types or use the ones
-that are included in **zio-lambda-event** and **zio-lambda-response**.
+zio-lambda depends on [**zio-json**](https://github.com/zio/zio-json) for decoding any event you send to it and enconding any response you send back to the Lambda service. You can either create your own data types or use the ones that are included in **zio-lambda-event** and **zio-lambda-response**.
 
 The last step is to define the way your function will be invoked. There are three ways, detailed below:
 
@@ -62,8 +57,7 @@ Each release will contain a zip file ready to be used as a lambda layer) and you
 
    ![binary-located](https://user-images.githubusercontent.com/14280155/164103337-6645dfeb-7fc4-4f7f-9b13-8005b0cddead.png)
 
-3. Create the following bootstap file (which calls out to the binary) and place it in the same directory alongside the
-   binary:
+3. Create the following bootstap file (which calls out to the binary) and place it in the same directory alongside the binary:
     ```bash
     #!/usr/bin/env bash
 
@@ -128,8 +122,7 @@ Create a Lambda function and choose container image:
 
 ![image](https://user-images.githubusercontent.com/14280155/164120764-2c736a46-29e3-488c-ba6a-e2b69ef51792.png)
 
-Please note that because you incur the overhead of your native binary residing within a Docker container, there is more
-overhead than the other approach of deploying the binary straight to AWS Lambda
+Please note that because you incur the overhead of your native binary residing within a Docker container, there is more overhead than the other approach of deploying the binary straight to AWS Lambda
 
 ## Documentation
 
@@ -148,7 +141,6 @@ See the [Code of Conduct](https://zio.dev/about/code-of-conduct)
 Come chat with us on [![Badge-Discord]][Link-Discord].
 
 [Badge-Discord]: https://img.shields.io/discord/629491597070827530?logo=discord "chat on discord"
-
 [Link-Discord]: https://discord.gg/2ccFBr4 "Discord"
 
 ## License

project/plugins.sbt

@@ -9,6 +9,6 @@ addSbtPlugin("com.github.sbt"            % "sbt-ci-release"      % "1.5.12")
 addSbtPlugin("com.eed3si9n"              % "sbt-assembly"        % "0.14.6")
 addSbtPlugin("com.github.sbt"            % "sbt-native-packager" % "1.9.16")
 addSbtPlugin("io.github.davidgregory084" % "sbt-tpolecat"        % "0.4.4")
-addSbtPlugin("dev.zio"                   % "zio-sbt-website"     % "0.3.10")
+addSbtPlugin("dev.zio"                   % "zio-sbt-website"     % "0.3.9")
 
 resolvers += Resolver.sonatypeRepo("public")