diff --git a/backend/src/main/java/edu/internet2/tier/shibboleth/admin/ui/controller/MetadataResolversController.java b/backend/src/main/java/edu/internet2/tier/shibboleth/admin/ui/controller/MetadataResolversController.java
index 2b4b90d65..7388679da 100644
--- a/backend/src/main/java/edu/internet2/tier/shibboleth/admin/ui/controller/MetadataResolversController.java
+++ b/backend/src/main/java/edu/internet2/tier/shibboleth/admin/ui/controller/MetadataResolversController.java
@@ -119,7 +119,7 @@ public ResponseEntity<?> create(@RequestBody MetadataResolver newResolver) throw
         positionOrderContainerService.appendPositionOrderForNew(persistedResolver);
 
         //TODO: currently, the update call might explode, but the save works.. in which case, the UI never gets
-        // an valid response. This operation is not atomic. Should we return an error here?
+        // n valid response. This operation is not atomic. Should we return an error here?
         updateChainingMetadataResolver(persistedResolver);
 
         return ResponseEntity.created(getResourceUriFor(persistedResolver)).body(persistedResolver);