diff --git a/design/src/rfcs/rfc0015_using_features_responsibly.md b/design/src/rfcs/rfc0015_using_features_responsibly.md
index 3e12ee0d4769245520ca82edeb5a87a5bf960797..2b018c64f41fecf591cf68501f659b1441a71d80 100644
--- a/design/src/rfcs/rfc0015_using_features_responsibly.md
+++ b/design/src/rfcs/rfc0015_using_features_responsibly.md
@@ -1,6 +1,6 @@
 # RFC: How Cargo "features" should be used in the SDK and runtime crates
 
-> Status: RFC
+> Status: Accepted
 
 ## Some background on features
 
diff --git a/design/src/rfcs/rfc0016_flexible_checksum_support.md b/design/src/rfcs/rfc0016_flexible_checksum_support.md
index dc95696d83609b671b39e11495716d43920888ee..aa0851c61913acdc7a7a41201f194c4998e067e1 100644
--- a/design/src/rfcs/rfc0016_flexible_checksum_support.md
+++ b/design/src/rfcs/rfc0016_flexible_checksum_support.md
@@ -1,7 +1,7 @@
 RFC: Supporting Flexible Checksums
 ==================================
 
-> Status: RFC
+> Status: Implemented
 
 We can't currently update the S3 SDK because we don't support the new "Flexible Checksums" feature. This RFC describes this new feature and details how we should implement it in `smithy-rs`.
 
diff --git a/design/src/rfcs/rfc0018_logging_sensitive.md b/design/src/rfcs/rfc0018_logging_sensitive.md
index 2fc1364907a5dd4195d9e2c650be8d2fda1965e3..f8905beec8d9dd52d748f054af46d25916def5bd 100644
--- a/design/src/rfcs/rfc0018_logging_sensitive.md
+++ b/design/src/rfcs/rfc0018_logging_sensitive.md
@@ -1,6 +1,6 @@
 # RFC: Logging in the Presence of Sensitive Data
 
-> Status: RFC
+> Status: Accepted
 
 Smithy provides a [sensitive trait](https://awslabs.github.io/smithy/1.0/spec/core/documentation-traits.html#sensitive-trait) which exists as a `@sensitive` field annotation syntactically and has the following semantics:
 
diff --git a/design/src/rfcs/rfc0019_event_streams_errors.md b/design/src/rfcs/rfc0019_event_streams_errors.md
index 2445cb252093ee1dbcd0860607b7d631086be5f1..35274276f08b0d1b84a99ed4830f3e94d1bc0b15 100644
--- a/design/src/rfcs/rfc0019_event_streams_errors.md
+++ b/design/src/rfcs/rfc0019_event_streams_errors.md
@@ -3,7 +3,7 @@ RFC: Errors for event streams
 =============
 
 <!-- RFCs start with the "RFC" status and are then either "Implemented" or "Rejected".  -->
-> Status: RFC
+> Status: Implemented
 
 <!-- A great RFC will include a list of changes at the bottom so that the implementor can be sure they haven't missed anything -->
 For a summarized list of proposed changes, see the [Changes Checklist](#changes-checklist) section.