Integrate README updates

Author: Shillaker

docs/development.md

@@ -0,0 +1,17 @@
+# Development
+
+To run Serverless Framework with a local checkout of this plugin, you can modify the `serverless.yml` for one or more functions as follows:
+
+```yaml
+...
+
+# Change this
+plugins:
+  - serverless-scaleway-functions
+
+# To this
+plugins:
+  - <path to checkout of this project>
+```
+
+Then you can run commands as normal.

docs/es-modules.md

@@ -9,7 +9,9 @@ Path to your handler file (from `serverless.yml`), omit `./`, `../`, and add the
     - secondHandler.js => module.exports.mySecondHandler = ...
 - serverless.yml
 ```
+
 In serverless.yml:
+
 ```yml
 provider:
   # ...
@@ -42,12 +44,12 @@ According to the official documentation, to use ES modules you can specify the m
 This then enables you to write your code for ES modules:
 
 ```javascript
-export {handle};
+export { handle };
 
 function handle (event, context, cb) {
     return {
         body: process.version,
-        headers: {"Content-Type": ["text/plain"]},
+        headers: { "Content-Type": ["text/plain"] },
         statusCode: 200,
     };
 };
@@ -56,6 +58,7 @@ function handle (event, context, cb) {
 The use of ES modules is encouraged since they are more efficient and make setup and debugging much easier.
 
 Note that using `"type": "module"` or `"type": "commonjs"` in your `package.json` file will enable or disable some features in Node runtime, such as:
+
 - `commonjs` is used as the default value
 - `commonjs` allows you to use `require/module.exports` (synchronous code loading - it basically copies all file contents)
 - `module` allows you to use `import/export` ES6 instructions (asynchronous loading - more optimized as it imports only the pieces of code you need)

docs/events.md

@@ -19,7 +19,8 @@ functions:
     # "events" is a list of triggers, the first key being the type of trigger.
     - schedule:
         # CRON Job Schedule (UNIX Format)
-        rate: '1 * * * *'
+        rate: "1 * * * *"
+
         # Input variable are passed in your function's event during execution
         input:
           key: value
@@ -33,10 +34,11 @@ custom:
   containers:
     mycontainer:
       directory: my-directory
+
       # Events key
       events:
         - schedule:
-            rate: '1 * * * *'
+            rate: "1 * * * *"
             input:
               key: value
               key2: value2

docs/golang.md

@@ -1,6 +1,7 @@
 # Golang
 
 Path to your handler's **package**. For example, if you have the following structure:
+
 ```yml
 - src
   - testing
@@ -10,7 +11,9 @@ Path to your handler's **package**. For example, if you have the following struc
 - serverless.yml
 - handler.go -> package main at the root of project
 ```
+
 Your serverless.yml `functions` should look something like this:
+
 ```yml
 provider:
   # ...

docs/python.md

@@ -9,7 +9,9 @@ Path to handler file `src/testing/handler.py`:
     - secondHandler.py => def my_second_handler
 - serverless.yml
 ```
+
 In serverless.yml:
+
 ```yml
 provider:
   # ...

docs/troubleshooting.md

@@ -0,0 +1,6 @@
+## Troubleshooting
+
+### Rate Limiting Issue
+
+If you are experiencing rate limiting issues (error 429) in your application, consider engaging with the support and/or the community. When seeking assistance, remember to provide relevant details, such as the specific rate limiting error messages, the affected components, and any relevant configuration information. This will enable us to better understand your situation and provide appropriate guidance or solutions.
+