Standardize Series 5 sections: remove Summary, rename Key Patterns to Key Design Decisions

Author: workcontrolgit

blogs/series-5-devops-data/5.1-database-seeding.md

@@ -460,17 +460,6 @@ When an E2E test suite needs a specific dataset before running, this is where yo
 
 ---
 
-## 🎓 Summary
-
-The AngularNetTutorial seeding system has four layers:
-
-* **Bogus `Faker<T>`** — fluent rule definitions with `.UseSeed()` for reproducibility, `PickRandom()` for FK references, and two-parameter lambdas for field-to-field dependencies
-* **`DatabaseSeeder`** — generates all four collections in dependency order (Departments → SalaryRanges → Positions → Employees)
-* **`DbInitializer.SeedData()`** — one-liner that adds all collections and saves
-* **`Program.cs`** — gates seeding to development only, respects `SkipDbSeed` flag, skips if data already exists
-
-The result: `dotnet run` produces a fully populated application in three seconds. Every developer starts with the same 1,000 employees, and automated tests can rely on consistent seed data.
-
 ## 🌟 Why This Matters
 
 Empty databases make demos unconvincing and make UI bugs invisible — you can't find pagination problems without enough rows to paginate. Starting with a Bogus-powered seeder that generates 1,000 realistic employees in three seconds means the application looks like a real HR system from day one, not a toy.

blogs/series-5-devops-data/5.2-cicd-github-actions.md

@@ -478,7 +478,7 @@ After a successful run, the Actions page shows:
 
 ---
 
-## 💡 Key Patterns
+## 🔑 Key Design Decisions
 
 **`fail-fast: false` with browser matrix.** Cross-browser bugs only surface when all browsers run. Cancelling Firefox because Chromium failed hides real issues.
 
@@ -492,18 +492,6 @@ After a successful run, the Actions page shows:
 
 ---
 
-## 🎓 Summary
-
-The GitHub Actions workflow provides three jobs for a complete CI pipeline:
-
-* **`test`** — matrix over Chromium/Firefox/WebKit, `npm ci`, browser install, `CI=true` Playwright run, artifact upload
-* **`report`** — `dorny/test-reporter` publishes JUnit results as a GitHub Check
-* **`comment-pr`** — `github-script` posts a browser status table to the PR
-
-`playwright.config.ts` adapts to CI automatically via `process.env.CI`: strict `forbidOnly`, two retries, single worker, and `open: 'never'` on the HTML reporter.
-
-The gap to close is service startup — adding `webServer` configuration or Docker Compose steps to start IdentityServer, the .NET API, and Angular before the test run. Once those services are live, the workflow runs the full OIDC-authenticated Playwright suite across all three browsers on every push and pull request.
-
 ## 🌟 Why This Matters
 
 A Playwright test suite that only runs locally isn't a CI/CD test suite — it's a manual checklist. GitHub Actions with browser matrix, artifact upload, JUnit reporting, and PR comments turns the same tests into an automated quality gate that runs on every push. The `process.env.CI` adaptations — `forbidOnly`, `retries: 2`, `workers: 1` — make the same test suite stable in CI without changing a single test.