Skip to content

Fixing language on a couple of public-facing documents #3419

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
briggs-octo merged 3 commits into from
Aug 25, 2026
Merged

Fixing language on a couple of public-facing documents #3419

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bf5652b
Fixing language on Platform Engineering > Enterprise Patterns page
briggs-octo Aug 25, 2026
32650c4
Updating modification date on Enterprise Patterns documentation
briggs-octo Aug 25, 2026
4bf941b
Update language/grammar in secret-variables.md
briggs-octo Aug 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/pages/docs/best-practices/platform-engineering/enterprise-patterns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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
Expand Down Expand Up @@ -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 |
Expand Down
4 changes: 2 additions & 2 deletions src/pages/docs/best-practices/platform-engineering/secret-variables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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
Expand Down Expand Up @@ -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.

Expand Down