Skip to content

Commit

Permalink
Fix typos
Browse files Browse the repository at this point in the history
  • Loading branch information
Sebastian Schöps committed Apr 6, 2020
1 parent 9979cfe commit d47f2c9
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,14 +28,14 @@ Just put the following in your Laravel code to send information to Loggy:
```
loggy($myMessage);
```
`myMessage` can be anything that can be tranlated into JSON (usually you would use a string or an array).
`myMessage` can be anything that can be translated into JSON (usually you would use a string or an array).

## More information
### Why?
When starting to work with Laravel Vapor we realized how great this product of the Laravel team is!
But our app showed different behaviour on the production system than in our development system.
Finding the issues was very hard because logging in the Vapor console is not as intuitive as we were used to from our local systems.
So we built a helper that just sends logging entries to a dashboard in realtime - "loggy" was born.
So we built a helper that just sends logging entries to a dashboard in realtime - "Loggy" was born.
We asked ourselves the question: why not open it to any Laravel developer? We found no negative answer, so: here we go!
And it's not just great for Vapor - it helps even with your local development.
### What does it do with my data?
Expand Down

0 comments on commit d47f2c9

Please sign in to comment.