diff --git a/CHANGELOG.md b/CHANGELOG.md
index 11c00ab3d..0772c4db8 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -17,11 +17,23 @@ and includes an additional section for migration notes.
 
 ### Migration Notes
 
-- For users upgrading from ORCA v8.x.x to v9.x.x follow the below steps before deploying:
-    1. Run the Lambda deletion script found in `python3 bin/delete_lambda.py` this will delete all of the ORCA Lambdas with a provided prefix. Or delete them manually in the AWS console.
-    2. Navigate to the AWS console and search for the Cumulus RDS security group.
-    3. Remove the inbound rule with the source of `PREFIX-vpc-ingress-all-egress` in Cumulus RDS security group.
-    4. Search for `PREFIX-vpc-ingress-all-egress` and delete the security group **NOTE:** Due to the Lambdas using ENIs, when deleting the securty groups it may say they are still associated with a Lambda that was deleted by the script. AWS may need a few minutes to refresh to fully disassociate the ENIs completely, if this error appears wait a few minutes and then try again.
+### Added
+
+### Changed
+
+### Deprecated
+
+### Removed
+
+### Fixed
+
+### Security
+
+## [9.0.2] 2024-01-26
+
+### Migration Notes
+
+If you are migrating from ORCA v8.x.x to this version, see the migration notes under v9.0.0.
 
 ### Added
 
@@ -81,7 +93,7 @@ and includes an additional section for migration notes.
 ### Migration Notes
 
 - Update terraform to the latest 1.5 version
-- For users upgrading from ORCA v8.x.x to v9.x.x follow the below steps before deploying:
+- For users upgrading from ORCA v8.x.x to v9.x.x, follow the below steps before deploying:
     1. Run the Lambda deletion script found in `python3 bin/delete_lambda.py` this will delete all of the ORCA Lambdas with a provided prefix. Or delete them manually in the AWS console.
     2. Navigate to the AWS console and search for the Cumulus RDS security group.
     3. Remove the inbound rule with the source of `PREFIX-vpc-ingress-all-egress` in Cumulus RDS security group.
diff --git a/website/docs/developer/deployment-guide/creating-orca-archive-bucket.md b/website/docs/developer/deployment-guide/creating-orca-archive-bucket.md
index 49f6fccec..957039e86 100644
--- a/website/docs/developer/deployment-guide/creating-orca-archive-bucket.md
+++ b/website/docs/developer/deployment-guide/creating-orca-archive-bucket.md
@@ -95,7 +95,7 @@ This will create archive and reports buckets with the necessary bucket policies
 
 ### Via Terraform
 
-The Terraform template for creating the ORCA DR buckets can be found [here](https://github.com/nasa/cumulus-orca/blob/master/modules/dr_buckets/dr_buckets.tf). Make sure you have AWS CLI installed and a DR profile for the DR account configured before deploying this template. More information on how to configure an AWS CLI profile can be found [here](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-options.html#cli-configure-options-list:~:text=as%20programmatically%20useful.-,%2D%2Dprofile%20%3Cstring%3E,-Specifies%20the%20named).
+The Terraform template for creating the ORCA DR buckets can be found [here](https://github.com/nasa/cumulus-orca/blob/master/modules/dr_buckets/dr_buckets.tf). Make sure you have AWS CLI installed and AWS configured to deploy to your DR account.
 
 From your terminal, first run `terraform init` followed by `terraform apply`. When running the apply, Terraform will ask for the following inputs:
 1. `cumulus_account_id` - This is the account ID of the Cumulus AWS account.
diff --git a/website/docs/developer/development-guide/code/versioning-releases.md b/website/docs/developer/development-guide/code/versioning-releases.md
index e044e545b..7076ff595 100644
--- a/website/docs/developer/development-guide/code/versioning-releases.md
+++ b/website/docs/developer/development-guide/code/versioning-releases.md
@@ -1,7 +1,6 @@
-
 ---
 id: versioning-releases
-title:  ORCA Versioning and Releases
+title: ORCA Versioning and Releases
 description: Provides information to developers on semantic versioning and the release process.
 ---