diff --git a/src/history/HistoryManagerImpl.cpp b/src/history/HistoryManagerImpl.cpp
index a9d43bbfaf..64c4e223a5 100644
--- a/src/history/HistoryManagerImpl.cpp
+++ b/src/history/HistoryManagerImpl.cpp
@@ -114,7 +114,7 @@ writeCheckpointFile(Application& app, HistoryArchiveState const& has,
         has.serialize(ar);
     }
 
-    // Immediately produce a final checkpoint JSON (suitable for confirmed
+    // Immediately produce a final checkpoint file (suitable for confirmed
     // ledgers)
     if (finalize)
     {
@@ -128,7 +128,7 @@ writeCheckpointFile(Application& app, HistoryArchiveState const& has,
     {
         auto out = HistoryManager::publishQueuePath(app.getConfig()) /
                    publishQueueTmpFileName(has.currentLedger);
-        // Otherwise, white a temporary durable file, to be finalized once
+        // Otherwise, write a temporary durable file, to be finalized once
         // has.currentLedger is actually committed
         fs::durableRename(
             tmpOut.string(), out.string(),
diff --git a/src/util/XDRStream.h b/src/util/XDRStream.h
index 36e293e703..c122183e53 100644
--- a/src/util/XDRStream.h
+++ b/src/util/XDRStream.h
@@ -236,7 +236,7 @@ class XDRInputFileStream
 IMPORTANT: some areas of core require durable writes that
 are resistant to application and system crashes. If you need durable writes:
 1. Use a stream implementation that supports fsync, e.g. OutputFileStream
-2. Write to a temp file first. If you don't intent to persist temp files across
+2. Write to a temp file first. If you don't intend to persist temp files across
 runs, fsyncing on close is sufficient. Otherwise, use durableWriteOne to flush
 and fsync after every write.
 3. Close the temp stream to make sure flush and fsync are called.