From cca05a1aa1b90aed5f5a3a5b80cbd0bb90b28f28 Mon Sep 17 00:00:00 2001 From: Christine Dodrill Date: Sat, 25 Mar 2017 11:04:21 -0700 Subject: [PATCH] blog/gopreload: fix typos --- blog/gopreload-2017-03-25.markdown | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/blog/gopreload-2017-03-25.markdown b/blog/gopreload-2017-03-25.markdown index cee1a92..9b54629 100644 --- a/blog/gopreload-2017-03-25.markdown +++ b/blog/gopreload-2017-03-25.markdown @@ -12,9 +12,9 @@ flag values, [debugging tools][manhole] or database drivers. With monorepo cultu prevalent in larger microservices based projects, this can lead to a few easily preventable problems: -- Forgetting to set up a logger default, causing errors reported to go nowhere - or metrics submission, making operations teams blind to the performance of the - app. +- Forgetting to set up a logger default or metrics submission, making operations + teams blind to the performance of the app and developer teams blind to errors + that come up during execution. - The requirement to make code changes to add things like metrics or HTTP routing extensions. @@ -90,4 +90,5 @@ on the Gophers slack (I'm `@xena` there). For issues with gopreload please file [go-plugins]: https://golang.org/pkg/plugin/ [manhole-tools]: https://github.com/Xe/gopreload/blob/master/manhole/server.go [ld-preload]: https://rafalcieslak.wordpress.com/2013/04/02/dynamic-linker-tricks-using-ld_preload-to-cheat-inject-features-and-investigate-programs/ +[twitter-addr]: https://twitter.com/theprincessxena [gopreload-issues]: https://github.com/Xe/gopreload/issues/new