diff --git a/FirebaseInAppMessaging/Sources/Analytics/FIRIAMClearcutUploader.m b/FirebaseInAppMessaging/Sources/Analytics/FIRIAMClearcutUploader.m
index 841cdeee1b3..a1a0646f5f3 100644
--- a/FirebaseInAppMessaging/Sources/Analytics/FIRIAMClearcutUploader.m
+++ b/FirebaseInAppMessaging/Sources/Analytics/FIRIAMClearcutUploader.m
@@ -177,7 +177,7 @@ - (void)attemptUploading {
                                * Note that there is a chance that the app crashes before we can
                                * call pushRecords: on the logStorage below which means we lost
                                * these log records permanently. This is a trade-off between handling
-                               * duplicate records on server side vs taking the risk of lossing
+                               * duplicate records on server side vs taking the risk of losing
                                * data. This implementation picks the latter.
                                */
                               FIRLogDebug(kFIRLoggerInAppMessaging, @"I-IAM260007",
diff --git a/FirebaseInAppMessaging/Sources/DefaultUI/ImageOnly/FIRIAMImageOnlyViewController.m b/FirebaseInAppMessaging/Sources/DefaultUI/ImageOnly/FIRIAMImageOnlyViewController.m
index 4fd7bf8a133..990aea253bb 100644
--- a/FirebaseInAppMessaging/Sources/DefaultUI/ImageOnly/FIRIAMImageOnlyViewController.m
+++ b/FirebaseInAppMessaging/Sources/DefaultUI/ImageOnly/FIRIAMImageOnlyViewController.m
@@ -117,7 +117,7 @@ - (void)viewDidLayoutSubviews {
 
   // Calculate the size of the image view under the constraints:
   // 1 Retain the image ratio
-  // 2 Have at least 30 point of margines around four sides of the image view
+  // 2 Have at least 30 point of margins around four sides of the image view
 
   CGFloat minimalMargine = 30;  // 30 points
   CGFloat maxImageViewWidth = self.view.window.frame.size.width - minimalMargine * 2;
diff --git a/FirebaseInAppMessaging/Sources/DefaultUI/Modal/FIRIAMModalViewController.m b/FirebaseInAppMessaging/Sources/DefaultUI/Modal/FIRIAMModalViewController.m
index ada6dd089e1..3009e38fc42 100644
--- a/FirebaseInAppMessaging/Sources/DefaultUI/Modal/FIRIAMModalViewController.m
+++ b/FirebaseInAppMessaging/Sources/DefaultUI/Modal/FIRIAMModalViewController.m
@@ -296,7 +296,7 @@ - (void)layoutFineTuneInPortraitMode {
                "with frame height as %lf",
               heightCalcReference, self.view.window.frame.size.height);
 
-  // this makes sure titleLable gets correct width to be ready for later's height estimate for the
+  // this makes sure titleLabel gets correct width to be ready for later's height estimate for the
   // text & button column
   [self.messageCardView layoutIfNeeded];
 
@@ -403,7 +403,7 @@ - (void)layoutFineTuneInLandscapeMode {
     self.cardLeadingMarginInLandscapeMode.constant = self.view.window.frame.size.width / 5;
   }
 
-  // this makes sure titleLable gets correct width to be ready for later's height estimate for the
+  // this makes sure titleLabel gets correct width to be ready for later's height estimate for the
   // text & button column
   [self.messageCardView layoutIfNeeded];
 
diff --git a/FirebaseInAppMessaging/Sources/DefaultUI/README.md b/FirebaseInAppMessaging/Sources/DefaultUI/README.md
index 872eff63623..c5200f50913 100644
--- a/FirebaseInAppMessaging/Sources/DefaultUI/README.md
+++ b/FirebaseInAppMessaging/Sources/DefaultUI/README.md
@@ -1,5 +1,5 @@
 FirebaseInAppMessagingDisplay is the default UI implementation from Firebase for
-rendering In-App Messaging messges to end users.
+rendering In-App Messaging messages to end users.
 
 Apps can also provide custom UI implementation to replace it. Check out our guides
 for details.