Resolving Review comments

project-copacetic · Dec 7, 2024 · 52087f6 · 52087f6
1 parent 4b350df
commit 52087f6
Show file tree

Hide file tree

Showing 4 changed files with 0 additions and 6 deletions.
diff --git a/website/docs/design.md b/website/docs/design.md
@@ -76,7 +76,6 @@ type PackageManager interface {
 
 ## Tradeoffs
 
-The core architectural choice of using packages as the unit of patching creates several constraints:
 
 1. **Package-Based Update Model**:
    - While Copa can work with or without vulnerability scanner reports, its patching capability is fundamentally based on os-level package updates

diff --git a/website/versioned_docs/version-v0.7.x/design.md b/website/versioned_docs/version-v0.7.x/design.md
@@ -76,8 +76,6 @@ type PackageManager interface {
 
 ## Tradeoffs
 
-The core architectural choice of using packages as the unit of patching creates several constraints:
-
 1. **Package-Based Update Model**:
    - While Copa can work with or without vulnerability scanner reports, its patching capability is fundamentally based on os-level package updates
    - When using scanner reports to perform a targeted patching of packages, false positives/negatives from scanners flow downstream to Copa

diff --git a/website/versioned_docs/version-v0.8.x/design.md b/website/versioned_docs/version-v0.8.x/design.md
@@ -76,7 +76,6 @@ type PackageManager interface {
 
 ## Tradeoffs
 
-The core architectural choice of using packages as the unit of patching creates several constraints:
 
 1. **Package-Based Update Model**:
    - While Copa can work with or without vulnerability scanner reports, its patching capability is fundamentally based on os-level package updates

diff --git a/website/versioned_docs/version-v0.9.x/design.md b/website/versioned_docs/version-v0.9.x/design.md
@@ -76,8 +76,6 @@ type PackageManager interface {
 
 ## Tradeoffs
 
-The core architectural choice of using packages as the unit of patching creates several constraints:
-
 1. **Package-Based Update Model**:
    - While Copa can work with or without vulnerability scanner reports, its patching capability is fundamentally based on os-level package updates
    - When using scanner reports to perform a targeted patching of packages, false positives/negatives from scanners flow downstream to Copa