Spelling (#1089)

* spelling: a hex

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: accepted

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: actions

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: additional

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: assertions

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: assessments

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: betta'

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: [br]eaking [ba]d

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: change

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: changed

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: childnodes

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: cleared

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: clusterrole

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: collection

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: columns

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: configuration

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: confirm

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: consensus

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: crumbs

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: ctrl

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: ctx

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: debugging

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: deltas

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: deprecated

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: describable

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: disturbance

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: disturbances

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: efforts

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: excitement

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: filter

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: forward

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: forwarding

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: fqn

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: fullscreen

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: grab

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: graphable

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: groups if

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: homebrew

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: hopeful

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: impatient

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: initialized

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: initially

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: is a

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: job runner

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: kubectl

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: kubernetes

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: latest

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: list

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: makusi

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: menu

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: mnemonic

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: nice

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: nominally

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: nonexistent

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: original

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: outputs

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: override

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: parens

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: preceded

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: preliminary

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: process

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: prozac

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: purpose

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: rbac

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: repeatedly

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: replenishing

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: resource

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: returns

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: right

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: row event

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: rpi

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: salient

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: seemingly

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: separator

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: shas

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: shortcut

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: shortcuts

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: solidify

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: sponsorship

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: superfluous

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: support

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: target's

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: threshold

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: times out

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: tripping

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: unanimous (?)

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: upgrade

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: using

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: views

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: vulnerability

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

* spelling: will launch

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

.golangci.yml

@@ -62,7 +62,7 @@ output:
 # all available settings of specific linters
 linters-settings:
   errcheck:
-    # report about not checking of errors in type assetions: `a := b.(MyStruct)`;
+    # report about not checking of errors in type assertions: `a := b.(MyStruct)`;
     # default is false: such cases aren't reported by default.
     check-type-assertions: true
 

.goreleaser.yml

@@ -45,7 +45,7 @@ changelog:
       - "^docs:"
       - "^test:"
 
-# Homebrews
+# Homebrew
 brews:
   - name: k9s
     tap:

README.md

@@ -250,7 +250,7 @@ K9s uses aliases to navigate most K8s resources.
 | View a Kubernetes resource using singular/plural or short-name | `:`po⏎                        | accepts singular, plural, short-name or alias ie pod or pods           |
 | View a Kubernetes resource in a given namespace                | `:`alias namespace⏎           |                                                                        |
 | Filter out a resource view given a filter                      | `/`filter⏎                    | Regex2 supported ie `fred|blee` to filter resources named fred or blee |
-| Inverse regex filer                                            | `/`! filter⏎                  | Keep everything that *doesn't* match.                                  |
+| Inverse regex filter                                           | `/`! filter⏎                  | Keep everything that *doesn't* match.                                  |
 | Filter resource view by labels                                 | `/`-l label-selector⏎         |                                                                        |
 | Fuzzy find a resource given a filter                           | `/`-f filter⏎                 |                                                                        |
 | Bails out of view/command/filter mode                          | `<esc>`                       |                                                                        |
@@ -710,7 +710,7 @@ You can style K9s based on your own sense of look and style. Skins are YAML file
 You can also change K9s skins based on the cluster you are connecting too. In this case, you can specify the skin file name as `$HOME/.k9s/mycontext_skin.yml`
 Below is a sample skin file, more skins are available in the skins directory in this repo, just simply copy any of these in your user's home dir as `skin.yml`.
 
-Colors can be defined by name or uing an hex representation. Of recent, we've added a color named `default` to indicate a transparent background color to preserve your terminal background color settings if so desired.
+Colors can be defined by name or using a hex representation. Of recent, we've added a color named `default` to indicate a transparent background color to preserve your terminal background color settings if so desired.
 
 > NOTE: This is very much an experimental feature at this time, more will be added/modified if this feature has legs so thread accordingly!
 

change_logs/release_0.1.1.md

@@ -15,7 +15,7 @@ rev and see if we're happier with some of the fixes!
 ## Change Logs
 
 + Added config file to tracks K9s configuration ~/.k9s/config.yml
-+ Changeg log file location to use Go tmp dir stdlib package.
++ Change log file location to use Go tmp dir stdlib package.
   Check the log destination and config file location using
     ```shell
     k9s info

change_logs/release_0.10.0.md

@@ -20,7 +20,7 @@ I would also like to take this opportunity to thank all of you for your kind PRs
 
 ## VatDoesDisDo?
 
-Most of the refactors are around K8s resource fetching and viewing as well as navigation changes. Based on our observations this release might load resources a bit slower than usual but should make navigation much faster once the cache is primed. We've made some improvements to be more consistent with navigation, menus and shortcuts management. We've got ride off the breadcrumbs navigation ie no more `p` to nav back. Crumbs are now just tracking a natural resoure navigation ie pod -> containers -> logs and no longer commands history. Each new command will now load a brand new breadcrumb. You can press `<esc>` to nav back to the previous page. We're also introducing a new hotkeys feature, that afforts creating shortcuts to navigate to your favorite resources ie shift-0 -> view pods, shift-1 -> view deployments (See HotKey section below). I know there were many outstanding PRS (Thank you to all that I've submitted!) and given the extent of the changes, I've resolved to incorporate them in manually vs having to deal with merge conflicts.
+Most of the refactors are around K8s resource fetching and viewing as well as navigation changes. Based on our observations this release might load resources a bit slower than usual but should make navigation much faster once the cache is primed. We've made some improvements to be more consistent with navigation, menus and shortcuts management. We've got ride off the breadcrumbs navigation ie no more `p` to nav back. Crumbs are now just tracking a natural resource navigation ie pod -> containers -> logs and no longer commands history. Each new command will now load a brand new breadcrumb. You can press `<esc>` to nav back to the previous page. We're also introducing a new hotkeys feature, that efforts creating shortcuts to navigate to your favorite resources ie shift-0 -> view pods, shift-1 -> view deployments (See HotKey section below). I know there were many outstanding PRS (Thank you to all that I've submitted!) and given the extent of the changes, I've resolved to incorporate them in manually vs having to deal with merge conflicts.
 
 ## Custom Skins Per Cluster
 
@@ -55,7 +55,7 @@ Feeling like you want to be able to quickly switch around your favorite resource
 
  Not feeling too `Hot`? No worried, your custom hotkeys list will be listed in the help view.`<?>`.
 
- You can choose any keyboard shotcuts that make sense to you, provided they are not part of the standard K9s shortcuts list.
+ You can choose any keyboard shortcuts that make sense to you, provided they are not part of the standard K9s shortcuts list.
 
 ## PullRequests
 

change_logs/release_0.11.0.md

@@ -16,7 +16,7 @@ Also if you dig this tool, please make some noise on social! [@kitesurfer](https
 
 ### Anyone At The Helm?
 
-K9s now offers prelimary support for Helm 3 charts! It's been a long time coming and I know a few early users had mentioned the need, but I wanted to see where Helm3 was going first. This is a preview release to see how we fair in Helm land. Besides managing your installed charts, you will be able to perform the following operations:
+K9s now offers preliminary support for Helm 3 charts! It's been a long time coming and I know a few early users had mentioned the need, but I wanted to see where Helm3 was going first. This is a preview release to see how we fair in Helm land. Besides managing your installed charts, you will be able to perform the following operations:
 
 * Uninstall a chart
 * View chart release notes
@@ -30,7 +30,7 @@ If you're using Helm3 in your current clusters, please give it a rip and also pi
 
 ### Bring Out Your Deads...
 
-There are also a few bugs fixes from the refactor aftermath that made this drop. I know this was a bit of a brutal transition, so thank you all for your patience and for filing issues! I am hopefull that K9s will stabilize quickly so we can move on to bigger things.
+There are also a few bugs fixes from the refactor aftermath that made this drop. I know this was a bit of a brutal transition, so thank you all for your patience and for filing issues! I am hopeful that K9s will stabilize quickly so we can move on to bigger things.
 
 ---
 

change_logs/release_0.11.3.md

@@ -16,7 +16,7 @@ Maintenance Release!
 
 ### Speedy Gonzales?
 
-In this drop, we took a bit of a perf pass in light of recent issues and thanks to [Chris Werner Rau](https://github.com/cwrau) pushing me and keeping me up to speed, I've digged a bit deeper and found that there might be some seamingly innocent calls that sucked a bit of cycles during K9s refreshes. Long story short, I think this drop will improve perf by a factor of ~10x in some instances. Typically the initial load will be slower but subsequent loads should be much faster. Famous last words right? Anyhow, can't really take credit for this one as the awesome [Gustavo Silva Paiva](https://github.com/paivagustavo) suggested doing this a while back, but since I was already in flight with the refactor decided to punt until back online. And here we are now...
+In this drop, we took a bit of a perf pass in light of recent issues and thanks to [Chris Werner Rau](https://github.com/cwrau) pushing me and keeping me up to speed, I've digged a bit deeper and found that there might be some seemingly innocent calls that sucked a bit of cycles during K9s refreshes. Long story short, I think this drop will improve perf by a factor of ~10x in some instances. Typically the initial load will be slower but subsequent loads should be much faster. Famous last words right? Anyhow, can't really take credit for this one as the awesome [Gustavo Silva Paiva](https://github.com/paivagustavo) suggested doing this a while back, but since I was already in flight with the refactor decided to punt until back online. And here we are now...
 
 Hopefully these findings will coalesce with yours?? If not, please forward bulk Prozac patches at the address below ;)
 

change_logs/release_0.12.0.md

@@ -12,7 +12,7 @@ Also if you dig this tool, please make some noise on social! [@kitesurfer](https
 
 ### Searchable Logs
 
-There has been quiet a few demands for this feature. It should now be generally available in this drop. It works the same as the resource view ie `/fred`, you can also specify a fuzzy filter using `/-f blee-duh`. The paint is still fresh on that deal and not super confident that it will work nominaly as I had to rework the logs to enable. So totally possible I've hosed something in the process.
+There has been quiet a few demands for this feature. It should now be generally available in this drop. It works the same as the resource view ie `/fred`, you can also specify a fuzzy filter using `/-f blee-duh`. The paint is still fresh on that deal and not super confident that it will work nominally as I had to rework the logs to enable. So totally possible I've hosed something in the process.
 
 ### APIServer Dud
 
@@ -21,7 +21,7 @@ At times, it could be you've lost your api server connection while K9s was up wh
 ### FullScreen Logs
 
 I've been told having a flag to set fullScreen mode preference while viewing the logs would be `awesome`. Thanks [Fardin Khanjani](https://github.com/fardin01)!
-So there is now a new K9s config flag available to set your fullsreen logs `drathers` in your .k9s/config.yml. This flag defaults to false if not set.
+So there is now a new K9s config flag available to set your fullscreen logs `drathers` in your .k9s/config.yml. This flag defaults to false if not set.
 
 Here is a snippet:
 

change_logs/release_0.3.1.md

@@ -14,7 +14,7 @@ Thank you so much for your support!!
 
 ## Change Logs
 
-1. Refactored a lot of code! So please watch for disturbence in the force!
+1. Refactored a lot of code! So please watch for disturbance in the force!
 1. Changed cronjob and job aliases names to `cj` and `jo` respectively
 1. *JobView*: Added new columns
    1. Completions

change_logs/release_0.3.3.md

@@ -17,7 +17,7 @@ Thank you so much for your support!!
 1. [Feature #131](https://github.com/derailed/k9s/issues/131)
    Preliminary support for snapcraft builds ie read trying this out...
 2. [Feature #118](https://github.com/derailed/k9s/issues/118) Add arm 32/64 bit builds.
-   NOTE: will need help vetting this out as my rpi cluster is currently down.
+   NOTE: will need help vetting this out as my RPi cluster is currently down.
 
 ---
 

change_logs/release_0.4.0.md

@@ -23,7 +23,7 @@ Thank you so much for your support and awesome suggestions to make K9s better!!
    4. Any verbs not in this standard K8s verb list, will end up in the EXTRAS column.
    5. For non resource URLS, we map standard REST verbs to K8s verbs ie post=create patch=update, etc..
    6. Added initial sorts by name and group while in RBAC view.
-   7. Usage: To activate, enter command mode via `:cr` or `:ro` for clusterole(cr)/role(ro), select a row and press `<enter>`
+   7. Usage: To activate, enter command mode via `:cr` or `:ro` for clusterrole(cr)/role(ro), select a row and press `<enter>`
    8. To bail out of the view and return to previous use `p` or `<esc>`
 2. One feature that was mentioned in the comments for the RBAC feature above Tx [faheem-cliqz](https://github.com/faheem-cliqz)! was the ability to check RBAC rules for a given user. Namely reverse RBAC lookup
    1. Added a new view, code name *Fu* view to show all the clusterroles/roles associated with a given user.

change_logs/release_0.4.1.md

@@ -37,7 +37,7 @@ Thank you so much for your support and awesome suggestions to make K9s better!!
 
 ### o ~~FuView~~ is now PolicyView
 
-  The Fu command has been depracated for pol(icy) command to see all RBAC policies available on a subject. You can use `pol` (instead of `fu`) to list out RBAC policies associated with a
+  The Fu command has been deprecated for pol(icy) command to see all RBAC policies available on a subject. You can use `pol` (instead of `fu`) to list out RBAC policies associated with a
   user/group or serviceaccount.
 
   ```text

change_logs/release_0.6.3.md

@@ -18,7 +18,7 @@ Also if you dig this tool, please make some noise on social! [@kitesurfer](https
 
 ### Performance... With feelings!
 
-Ran thru another perf pass and hope I've pushed the needle in the right direction? K9s is now leveraging informers which I think came out of CRDs work. Our initial assessments shows numbers to μsecond updates, down from milliseconds 🎉. Hopefully the ouputs are still correct as I have the tendency to make things much faster with incorrect results ;( We hope to hear back from you with a report from your clusters and assements and brace for good news? This was a deep cycle thru K9s core and more perf will be gain, once we get a chance to vet this new strategy. I'd like to take this opportunity to thank you all for your patience and incredible kindness and support. We certainly hope this drop won't turn out to be a dud as I am fresh out of prosac patches 😩
+Ran thru another perf pass and hope I've pushed the needle in the right direction? K9s is now leveraging informers which I think came out of CRDs work. Our initial assessments shows numbers to μsecond updates, down from milliseconds 🎉. Hopefully the outputs are still correct as I have the tendency to make things much faster with incorrect results ;( We hope to hear back from you with a report from your clusters and assessments and brace for good news? This was a deep cycle thru K9s core and more perf will be gain, once we get a chance to vet this new strategy. I'd like to take this opportunity to thank you all for your patience and incredible kindness and support. We certainly hope this drop won't turn out to be a dud as I am fresh out of prozac patches 😩
 
 ---
 

change_logs/release_0.7.0.md

@@ -16,9 +16,9 @@ Also if you dig this tool, please make some noise on social! [@kitesurfer](https
 
 I always seem to get this wrong... Does Labor Day weekend mean you get to work on your OSS projects all weekend?
 
-I am very excited about this drop and hopefully won't be hunamimous on this? 🐭
+I am very excited about this drop and hopefully won't be unanimous (?) on this? 🐭
 
-For the impatients watch this! [K9s v0.7.0 Features](https://youtu.be/83jYehwlql8)
+For the impatient watch this! [K9s v0.7.0 Features](https://youtu.be/83jYehwlql8)
 
 ### Service Traversals
 
@@ -28,7 +28,7 @@ Provided your K8s services are head(Full), you can now navigate to the pods that
 
 In this drop, we've added support for port-forwarding that allows you to exercise your container from your local machine. To setup a port-forward, from the Pod view drill down to a selected Pod's containers, select the container that exposes the port of interest and hit `Ctrl-F`. A dialog will popup allowing you to configure a localhost port to forward to. Once set up, K9s will take you to you to the new PortForward view aka `pf`. Pending your terminal feature and container setup, you should be able to pop the forwarded URL directly into your browse. On iTerm2 me think `command+click` does the trick?
 
-Big thanks and ATTABOY! in full effect all week to [Brent](https://github.com/brentco) for filing this initial issue. Please keep in mind, these port-forward babies are a bit expensive to run, so make sure you choose wisely and delete any superflous PFs!!
+Big thanks and ATTABOY! in full effect all week to [Brent](https://github.com/brentco) for filing this initial issue. Please keep in mind, these port-forward babies are a bit expensive to run, so make sure you choose wisely and delete any superfluous PFs!!
 
 This feature is still work in progress. It does require a new config file to help assist with URL configurations. As it stands, your PortForwards are in effect for the current K9s session and will be terminated on exit. Please thread lightly and checkout the README under the Benchmarking section. Your feedback on this as always, is welcome and encouraged!
 
@@ -40,7 +40,7 @@ Benchmarking is enabled via keyboard shortcuts `Ctrl-B` and `Alt-B` to activate/
 
 So you now have the ability to stretch out your cluster legs by benchmarking your pods and services and gather all kind of interesting statistics directly in K9s. Generating load on your resources will help you tune your cluster resources, exercise your auto scalers, compare Canary builds perf, etc...
 
-Please keep in mind, this is very much a moving target at this point and will change. Ingress support will come next once we solidy the existing feature. Also checkout the README for additional configuration for this feature. With the understanding the Full Monty is coming, please help us solidify these features as these are the base ingredients to even cooler things coming down the line...
+Please keep in mind, this is very much a moving target at this point and will change. Ingress support will come next once we solidify the existing feature. Also checkout the README for additional configuration for this feature. With the understanding the Full Monty is coming, please help us solidify these features as these are the base ingredients to even cooler things coming down the line...
 
 > NOTE! As with anything in life `Aim small, Miss small!`. You could totally overwhelm K9s with over-zealous benchmarks and port-forwards, so please start small say C:1 N:1000, measure and go from there.
 
@@ -53,7 +53,7 @@ Please keep in mind, this is very much a moving target at this point and will ch
 + [Issue #195](https://github.com/derailed/k9s/issues/195) Thanks to the awesome [Sebastiaan](https://github.com/tammert). You Rock Sir!!
 + [Issue #194](https://github.com/derailed/k9s/issues/194)
 + [Issue #187](https://github.com/derailed/k9s/issues/187)
-+ [Issue #119](https://github.com/derailed/k9s/issues/119) Added `Ctrl-S` shorcut to dump table data as csv and log data as text.
++ [Issue #119](https://github.com/derailed/k9s/issues/119) Added `Ctrl-S` shortcut to dump table data as csv and log data as text.
 + [Issue #69](https://github.com/derailed/k9s/issues/69)
 
 ---

change_logs/release_0.7.5.md

@@ -13,7 +13,7 @@ Also if you dig this tool, please make some noise on social! [@kitesurfer](https
 ## Change Logs
 
 Rats, looks like 0.7.4 is a dud! Sorry my fault, feeling burned out ;(
-Please ugrade to 0.7.5. Thank you for your patience and support!
+Please upgrade to 0.7.5. Thank you for your patience and support!
 
 ---