From bf5652b85fe8f7c5475bcd83b84c3d79a766b67b Mon Sep 17 00:00:00 2001
From: Britton Riggs <104870596+briggs-octo@users.noreply.github.com>
Date: Tue, 25 Aug 2026 09:12:29 -0700
Subject: [PATCH 1/3] Fixing language on Platform Engineering > Enterprise
 Patterns page

---
 .../best-practices/platform-engineering/enterprise-patterns.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/pages/docs/best-practices/platform-engineering/enterprise-patterns.md b/src/pages/docs/best-practices/platform-engineering/enterprise-patterns.md
index c3268c6d85..f659898bb0 100644
--- a/src/pages/docs/best-practices/platform-engineering/enterprise-patterns.md
+++ b/src/pages/docs/best-practices/platform-engineering/enterprise-patterns.md
@@ -170,7 +170,7 @@ You need to synchronize the Octopus installations to ensure their configuration
 
 Unlike the previous patterns, this pattern is less concerned with providing the ability for teams and customers to log into Octopus installations. Rather, DevOps teams use non-production Octopus installations to test upgrades and validate project changes.
 
-This pattern may also use used to isolate Octopus installations for compliance reasons, such as PCI. Having a separate Octopus installation for the production environment makes it easy demonstrate access controls and other security measures when undertaking
+This pattern may also be used to isolate Octopus installations for compliance reasons, such as PCI. Having a separate Octopus installation for the production environment makes it easy to demonstrate access controls and other security measures when undertaking
 security audits.
 
 | Feature                                          | Solves |

From 32650c4db62ca2e74765c8898943ede179534ebd Mon Sep 17 00:00:00 2001
From: Britton Riggs <104870596+briggs-octo@users.noreply.github.com>
Date: Tue, 25 Aug 2026 09:22:40 -0700
Subject: [PATCH 2/3] Updating modification date on Enterprise Patterns
 documentation

---
 .../best-practices/platform-engineering/enterprise-patterns.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/pages/docs/best-practices/platform-engineering/enterprise-patterns.md b/src/pages/docs/best-practices/platform-engineering/enterprise-patterns.md
index f659898bb0..e28e780c35 100644
--- a/src/pages/docs/best-practices/platform-engineering/enterprise-patterns.md
+++ b/src/pages/docs/best-practices/platform-engineering/enterprise-patterns.md
@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-01-01
-modDate: 2025-02-20
+modDate: 2026-08-25
 title: Octopus enterprise patterns
 description: This section describes common patterns for deploying octopus in enterprise environments.
 navOrder: 2

From 4bf941b5d6a620a101b1f0125cec56bcdcb8c81c Mon Sep 17 00:00:00 2001
From: Britton Riggs <104870596+briggs-octo@users.noreply.github.com>
Date: Tue, 25 Aug 2026 09:23:51 -0700
Subject: [PATCH 3/3] Update language/grammar in secret-variables.md

---
 .../best-practices/platform-engineering/secret-variables.md   | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/pages/docs/best-practices/platform-engineering/secret-variables.md b/src/pages/docs/best-practices/platform-engineering/secret-variables.md
index 0de2f8f5c6..00dfd7b6b2 100644
--- a/src/pages/docs/best-practices/platform-engineering/secret-variables.md
+++ b/src/pages/docs/best-practices/platform-engineering/secret-variables.md
@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-11-23
-modDate: 2023-11-23
+modDate: 2026-08-25
 title: Secret variables
 description: Learn how to export projects with secret variables
 navOrder: 11
@@ -112,7 +112,7 @@ Following these rules ensures the Octostache templates defining the default valu
 Dedicating an environment to the process of serializing and deploying downstream projects allows the upstream environment to scope sensitive variables such that:
 
 - They are made available when deploying downstream projects
-- They dot no leak into any regular deployment environments
+- They do not leak into any regular deployment environments
 
 This documentation and the step templates assumes this environment is called `Sync`. The `Sync` environment must not appear in the lifecycle of regular deployments, which ensures any variables scoped to the `Sync` environment do not leak into regular deployments.