diff --git a/configs.go b/configs.go
index fef0328..1831337 100644
--- a/configs.go
+++ b/configs.go
@@ -1807,7 +1807,7 @@ func (config ShippingConfig) params() (Params, error) {
 	return params, err
 }
 
-// PreCheckoutConfig conatins information for answerPreCheckoutQuery request.
+// PreCheckoutConfig contains information for answerPreCheckoutQuery request.
 type PreCheckoutConfig struct {
 	PreCheckoutQueryID string // required
 	OK                 bool   // required
diff --git a/docs/getting-started/README.md b/docs/getting-started/README.md
index 2ca050e..25b77f7 100644
--- a/docs/getting-started/README.md
+++ b/docs/getting-started/README.md
@@ -103,7 +103,7 @@ things. We can add this code in right after the line enabling debug mode.
 	}
 ```
 
-Congradulations! You've made your very own bot!
+Congratulations! You've made your very own bot!
 
 Now that you've got some of the basics down, we can start talking about how the
 library is structured and more advanced features.
diff --git a/docs/getting-started/important-notes.md b/docs/getting-started/important-notes.md
index d6388aa..9925b8a 100644
--- a/docs/getting-started/important-notes.md
+++ b/docs/getting-started/important-notes.md
@@ -43,7 +43,7 @@ pull request!
 
 - By default, bots only get updates directly addressed to them. If you need to
   get all messages, you must disable privacy mode with Botfather. Bots already
-  added to groups will need to be removed and readded for the changes to take
+  added to groups will need to be removed and re-added for the changes to take
   effect. You can read more on the [Telegram Bot API docs][api-docs].
 
 [api-docs]: https://core.telegram.org/bots/faq#what-messages-will-my-bot-get
diff --git a/docs/internals/uploading-files.md b/docs/internals/uploading-files.md
index 45d69bf..1845269 100644
--- a/docs/internals/uploading-files.md
+++ b/docs/internals/uploading-files.md
@@ -74,8 +74,8 @@ mediaGroup := NewMediaGroup(ChatID, []interface{}{
 })
 ```
 
-A `MediaGroupConfig` stores all of the media in an array of interfaces. We now
-have all of the data we need to upload, but how do we figure out field names for
+A `MediaGroupConfig` stores all the media in an array of interfaces. We now
+have all the data we need to upload, but how do we figure out field names for
 uploads? We didn't specify `attach://unique-file` anywhere.
 
 When the library goes to upload the files, it looks at the `params` and `files`
diff --git a/helpers.go b/helpers.go
index 8220e74..561919d 100644
--- a/helpers.go
+++ b/helpers.go
@@ -567,7 +567,7 @@ func NewEditMessageText(chatID int64, messageID int, text string) EditMessageTex
 	}
 }
 
-// NewEditMessageTextAndMarkup allows you to edit the text and replymarkup of a message.
+// NewEditMessageTextAndMarkup allows you to edit the text and reply markup of a message.
 func NewEditMessageTextAndMarkup(chatID int64, messageID int, text string, replyMarkup InlineKeyboardMarkup) EditMessageTextConfig {
 	return EditMessageTextConfig{
 		BaseEdit: BaseEdit{
diff --git a/types.go b/types.go
index cb77528..75e6101 100644
--- a/types.go
+++ b/types.go
@@ -290,7 +290,7 @@ type Chat struct {
 	// optional
 	Permissions *ChatPermissions `json:"permissions,omitempty"`
 	// SlowModeDelay is for supergroups, the minimum allowed delay between
-	// consecutive messages sent by each unpriviledged user. Returned only in
+	// consecutive messages sent by each unprivileged user. Returned only in
 	// getChat.
 	//
 	// optional