diff --git a/src/hotspot/share/gc/shenandoah/heuristics/shenandoahAdaptiveHeuristics.cpp b/src/hotspot/share/gc/shenandoah/heuristics/shenandoahAdaptiveHeuristics.cpp
index c9886ffb9ab..d5302ef8723 100644
--- a/src/hotspot/share/gc/shenandoah/heuristics/shenandoahAdaptiveHeuristics.cpp
+++ b/src/hotspot/share/gc/shenandoah/heuristics/shenandoahAdaptiveHeuristics.cpp
@@ -283,7 +283,7 @@ bool ShenandoahAdaptiveHeuristics::should_start_gc() {
   //       pass.  The best prediction for this aspect of spikes in allocation patterns is probably recent past history.
   //
   //  Rationale:
-  //    The idea is that there is an average allocation rate and there are occassional abnormal bursts (or spikes) of
+  //    The idea is that there is an average allocation rate and there are occasional abnormal bursts (or spikes) of
   //    allocations that exceed the average allocation rate.  What do these spikes look like?
   //
   //    1. At certain phase changes, we may discard large amounts of data and replace it with large numbers of newly
diff --git a/src/hotspot/share/gc/shenandoah/shenandoahFreeSet.cpp b/src/hotspot/share/gc/shenandoah/shenandoahFreeSet.cpp
index 881f7844183..40e33bb0d21 100644
--- a/src/hotspot/share/gc/shenandoah/shenandoahFreeSet.cpp
+++ b/src/hotspot/share/gc/shenandoah/shenandoahFreeSet.cpp
@@ -299,7 +299,7 @@ HeapWord* ShenandoahFreeSet::try_allocate_in(ShenandoahHeapRegion* r, Shenandoah
       } else {
         assert(r->affiliation() == ShenandoahRegionAffiliation::OLD_GENERATION, "GC Alloc was not YOUNG so must be OLD");
 
-        assert(req.type() != _alloc_gclab, "old-gen allocations use PLAB or shared allocation");
+        assert(req.type() != ShenandoahAllocRequest::_alloc_gclab, "old-gen allocations use PLAB or shared allocation");
         _heap->old_generation()->increase_used(size * HeapWordSize);
         // for plabs, we'll sort the difference between evac and promotion usage when we retire the plab
       }