diff --git a/translations/README.md b/translations/README.md
index 2091f50a1c8..9f1590eaabc 100644
--- a/translations/README.md
+++ b/translations/README.md
@@ -19,14 +19,14 @@ simple regular expression based wrapping of strings. It can always
 use improvements to understand additional strings.
 
 ## Extracting strings
-Once the strings are wrapped, you can extract strings from go files using 
+Once the strings are wrapped, you can extract strings from go files using
 the `go-xgettext` command which can be installed with:
 
 ```console
 go get github.com/gosexy/gettext/go-xgettext
 ```
 
-Once that's installed you can run `hack/update-translations.sh`, which
+Once that's installed you can run `./hack/update-translations.sh`, which
 will extract and sort any new strings.
 
 ## Adding new translations
@@ -34,14 +34,14 @@ Edit the appropriate `k8s.po` file, `poedit` is a popular open source tool
 for translations. You can load the `translations/kubectl/template.pot` file
 to find messages that might be missing.
 
-Once you are done with your `.po` file, generate the corresponding `k8s.mo`
-file. `poedit` does this automatically on save, but you can also use
-`hack/update-translations.sh` to perform the `po` to `mo` translation.
+Once you are done with your `k8s.po` file, generate the corresponding `k8s.mo`
+file. `poedit` does this automatically on save, but you can also run
+`./hack/update-translations.sh` to perform the `po` to `mo` translation.
 
 We use the English translation as the `msgid`.
 
 ## Regenerating the bindata file
-Run `./hack/generate-bindata.sh, this will turn the translation files
+Run `./hack/generate-bindata.sh`, this will turn the translation files
 into generated code which will in turn be packaged into the Kubernetes
 binaries.