docs(cli-client/skill): fix small typos in skill references

- spec-driven-testing.md: `Singing in and out` → `Signing in and out`
- storage-state.md: bump example cookie `expires` from 1735689600
  (Jan 1, 2025) to 1893456000 (Jan 1, 2030) so the example doesn't
  read as already-expired
- video-recording.md: `pulling appropriate pauses` → `inserting
  appropriate pauses`

Same fixes were originally opened as microsoft/playwright-cli#412;
@dgozman pointed out this is the source of truth, redoing it here.

Author: AllDmeat

packages/playwright-core/src/tools/cli-client/skill/references/spec-driven-testing.md

@@ -191,7 +191,7 @@ Collect the generated code and write the test file at the path given in the spec
 // seed: tests/seed.spec.ts
 import { test, expect } from './fixtures';   // or '@playwright/test' if no fixtures file
 
-test.describe('Singing in and out', () => {
+test.describe('Signing in and out', () => {
   test('should sign in', async ({ page }) => {
     // 1. Navigate to the application
     // (handled by the seed fixture)

packages/playwright-core/src/tools/cli-client/skill/references/storage-state.md

@@ -38,7 +38,7 @@ The saved file contains:
       "value": "abc123",
       "domain": "example.com",
       "path": "/",
-      "expires": 1735689600,
+      "expires": 1893456000,
       "httpOnly": true,
       "secure": true,
       "sameSite": "Lax"
@@ -92,7 +92,7 @@ playwright-cli cookie-set session abc123
 playwright-cli cookie-set session abc123 --domain=example.com --path=/ --httpOnly --secure --sameSite=Lax
 
 # Cookie with expiration (Unix timestamp)
-playwright-cli cookie-set remember_me token123 --expires=1735689600
+playwright-cli cookie-set remember_me token123 --expires=1893456000
 ```
 
 ### Delete a Cookie

packages/playwright-core/src/tools/cli-client/skill/references/video-recording.md

@@ -40,7 +40,7 @@ playwright-cli video-start recordings/checkout-test-run-42.webm
 ### 2. Record entire hero scripts.
 
 When recording a video for the user or as a proof of work, it is best to create a code snippet and execute it with run-code.
-It allows pulling appropriate pauses between the actions and annotating the video. There are new Playwright APIs for that.
+It allows inserting appropriate pauses between the actions and annotating the video. There are new Playwright APIs for that.
 
 1) Perform scenario using CLI and take note of all locators and actions. You'll need those locators to request their bounding boxes for highlight.
 2) Create a file with the intended script for video (below). Use pressSequentially w/ delay for nice typing, make reasonable pauses.