Tidy docs wording

website/blog/2019-05-27-compiling-benthos-to-wasm.md

@@ -162,7 +162,7 @@ There weren't any.
 ## Final Words
 
 It took a day for me to get a working application together and soon I'll be
-blogging about the resulting product. Web assembly with Go is dope.
+blogging about the resulting product. Web assembly with Go is yummy.
 
 Kudos to both the W3C and the Go team for taking their time to build something
 to completion without rushing the conclusion. Yes, I'm still bitter about Game

website/blog/2021-01-04-v4-roadmap.md

@@ -15,7 +15,7 @@ keywords: [
 tags: [ "v4" ]
 ---
 
-Benthos has been at major version 3 for over a year now, and I consider it to be a pretty cool achievement that given [all the dope features added](https://github.com/Jeffail/benthos/blob/master/CHANGELOG.md) we've managed to keep both the Benthos config spec and APIs fully backwards compatible.
+Benthos has been at major version 3 for over a year now, and I consider it to be a pretty cool achievement that given [all the great features added](https://github.com/Jeffail/benthos/blob/master/CHANGELOG.md) we've managed to keep both the Benthos config spec and APIs fully backwards compatible.
 
 However, eventually it would be nice to cut a new major release and prune all of the dead weight that has accumulated during this time. Since major version releases don't come often I wanted to be sure that we've considered and planned any other potential breaking changes that could be bundled along with it.
 
@@ -59,7 +59,7 @@ Sometimes it's nice to slow things down, this issue would allow us to configure
 
 [Click here to access the issue.](https://github.com/Jeffail/benthos/issues/590)
 
-This would allow you to create reusable, parameterized, configuration templates and have them natively supported within Benthos. This issue is pretty dope but also a significant amount of work, it could easily result in breaking changes being required and so I'd like to have this at least planned out and understood before v4.
+This would allow you to create reusable, parameterized, configuration templates and have them natively supported within Benthos. This issue is pretty great but also a significant amount of work, it could easily result in breaking changes being required and so I'd like to have this at least planned out and understood before v4.
 
 ### Improved Logging
 

website/cookbooks/joining_streams.md

@@ -15,8 +15,8 @@ Articles are received over the topic `articles` and look like this:
   "type": "article",
   "article": {
     "id": "123foo",
-    "title": "Dope article",
-    "content": "this is a totally dope article"
+    "title": "Good article",
+    "content": "this is a totally good article"
   },
   "user": {
     "id": "user1"
@@ -32,7 +32,7 @@ Comments can either be posted on an article or a parent comment, are received ov
   "comment": {
     "id": "456bar",
     "parent_id": "123foo",
-    "content": "this article sucks"
+    "content": "this article is bad"
   },
   "user": {
     "id": "user2"
@@ -48,11 +48,11 @@ Our goal is to end up with a single stream of comments, where information about
   "comment": {
     "id": "456bar",
     "parent_id": "123foo",
-    "content": "this article sucks"
+    "content": "this article is bad"
   },
   "article": {
-    "title": "Dope article",
-    "content": "this is a totally dope article"
+    "title": "Good article",
+    "content": "this is a totally good article"
   },
   "user": {
     "id": "user2"

website/docs/configuration/interpolation.md

@@ -30,10 +30,10 @@ Some Benthos fields also support [Bloblang][bloblang] function interpolations, w
 output:
   kafka:
     addresses: [ "TODO:6379" ]
-    topic: 'dope-${! json("topic") }'
+    topic: 'meow-${! json("topic") }'
 ```
 
-A message with the contents `{"topic":"foo","message":"hello world"}` would be routed to the Kafka topic `dope-foo`.
+A message with the contents `{"topic":"foo","message":"hello world"}` would be routed to the Kafka topic `meow-foo`.
 
 If a literal string is required that matches this pattern (`${!foo}`) then, similar to environment variables, you can escape it with double brackets. For example, the string `${{!foo}}` would be read as the literal `${!foo}`.