diff --git a/docs/developer/cloning-databases.md b/docs/developer/cloning-databases.md
index a193e4685..3c8a3c3fa 100644
--- a/docs/developer/cloning-databases.md
+++ b/docs/developer/cloning-databases.md
@@ -1,6 +1,6 @@
 # Cloning Databases
 The clone-db workflow clones a Source database to a Destination database using cloud.gov's cg-manage-rds tool. This document contains additional information needed to understand how the workflow functions.
-
+ 
 ## Additional Roles Required
 The clone-db workflow functions by temporarily sharing the Destination database with the space of the Source database. This is because cloning databases across spaces is hard. Sharing is done via the `cf share-service` command, but requires that the authenticated user (in this case this will be a user from the Source space) have the `space-developer` role in *both* the Source and Destination spaces. This must be set by someone with permission to edit space roles *before* the workflow runs. The user in question can be found using the `cf space-users [ORG] [SPACE]` command where the SPACE is the Source space, and will appear as a UAA user with a UUID as the name. There is only one such user per space by default (this is a [service account](https://cloud.gov/docs/services/cloud-gov-service-account/) set up by cloud.gov for our Github workflows). This user needs to be provided with the `space-developer` role in the Destination space, which can be accomplished using `cf set-space-role [USER] [ORG] [DESTINATION SPACE] SpaceDeveloper`.
 
diff --git a/src/registrar/config/settings.py b/src/registrar/config/settings.py
index 0111245a1..a58e3e2f9 100644
--- a/src/registrar/config/settings.py
+++ b/src/registrar/config/settings.py
@@ -520,7 +520,7 @@ LOGGING = {
             "()": JsonFormatter,
         },
     },
-    # define where log messages will be sent;
+    # define where log messages will be sent
     # each logger can have one or more handlers
     "handlers": {
         "console": {