docs: standardize multi-line text formatting in diagrams and tables by replacing HTML line breaks with hyphens.

Author: sayuru-akash

01-curriculum/01-requirements-engineering.md

@@ -40,9 +40,9 @@ Think of requirements as a pyramid - each level builds on the foundation below:
 
 ```mermaid
 graph TD
-    A[Business Requirements<br/>"Why are we building this?"] --> B[User Requirements<br/>"What do users need?"]
-    B --> C[Functional Requirements<br/>"What should it do?"]
-    C --> D[Non-Functional Requirements<br/>"How well should it do it?"]
+    A[Business Requirements - Why are we building this] --> B[User Requirements - What do users need]
+    B --> C[Functional Requirements - What should it do]
+    C --> D[Non-Functional Requirements - How well should it do it]
 
     style A fill:#e1f5ff
     style B fill:#fff4e1

01-curriculum/03-strategy-analysis.md

@@ -66,8 +66,8 @@ graph TB
 
 | Block                      | Description                                                                                   |
 | -------------------------- | --------------------------------------------------------------------------------------------- |
-| **Customer Segments**      | 1) Diners (urban professionals, 25-45) <br/> 2) Restaurants (casual dining, 20-100 seats)     |
-| **Value Propositions**     | Diners: Book in 60 sec, guaranteed seating <br/> Restaurants: Reduce no-shows from 30% to <5% |
+| **Customer Segments**      | 1) Diners (urban professionals, 25-45)  -  2) Restaurants (casual dining, 20-100 seats)     |
+| **Value Propositions**     | Diners: Book in 60 sec, guaranteed seating  -  Restaurants: Reduce no-shows from 30% to <5% |
 | **Channels**               | Web app (mobile-responsive), restaurant partner outreach, social media ads                    |
 | **Customer Relationships** | Self-service platform, automated SMS, dedicated restaurant success team                       |
 | **Revenue Streams**        | 10% commission on completed bookings                                                          |
@@ -104,7 +104,7 @@ Analyzes industry attractiveness and competitive intensity.
 
 ```mermaid
 mindmap
-  root((Restaurant<br/>Reservation<br/>Market))
+  root((Restaurant - Reservation - Market))
     Threat of New Entrants
       Low barriers technical
       High barriers network effects
@@ -217,7 +217,7 @@ sequenceDiagram
     Diner->>Host: Provide name & phone
     Host->>Paper Book: Write booking
     Host->>Diner: "See you then!" (verbal only)
-    Note over Diner: No confirmation<br/>Anxiety!
+    Note over Diner: No confirmation - Anxiety!
 ```
 
 **Pain Points:**
@@ -251,7 +251,7 @@ sequenceDiagram
     SMS Gateway-->>Diner: SMS within 30 sec
     App->>Restaurant Dashboard: New booking notification
     App-->>Diner: Confirmation page
-    Note over Diner: Peace of mind!<br/>Proof of booking
+    Note over Diner: Peace of mind! - Proof of booking
 ```
 
 **Improvements:**

01-curriculum/04-data-analytics.md

@@ -91,10 +91,10 @@ Also called **Pirate Metrics** (AARRR = "Arrr!"). Tracks users through 5 stages:
 
 ```mermaid
 graph LR
-    A[Acquisition<br/>How users find you] --> B[Activation<br/>First good experience]
-    B --> C[Retention<br/>Come back]
-    C --> D[Revenue<br/>Pay us]
-    D --> E[Referral<br/>Tell others]
+    A[Acquisition - How users find you] --> B[Activation - First good experience]
+    B --> C[Retention - Come back]
+    C --> D[Revenue - Pay us]
+    D --> E[Referral - Tell others]
 
     style A fill:#e1f5ff
     style B fill:#fff4e1
@@ -321,8 +321,8 @@ ORDER BY bookings DESC;
 
 ```mermaid
 graph LR
-    A[users table<br/>user_id, name, email] ---|user_id| B[bookings table<br/>booking_id, user_id, restaurant_id]
-    B ---|restaurant_id| C[restaurants table<br/>restaurant_id, name, cuisine]
+    A[users table - user_id, name, email] ---|user_id| B[bookings table - booking_id, user_id, restaurant_id]
+    B ---|restaurant_id| C[restaurants table - restaurant_id, name, cuisine]
 ```
 
 ```sql

01-curriculum/05-product-process.md

@@ -46,10 +46,10 @@ Learn the **ceremonies, artifacts, and rhythms** of modern product teams. This m
 
 ```mermaid
 graph LR
-    A[Sprint Planning<br/>4 hours] --> B[Daily Standups<br/>15 min/day]
-    B --> C[Development Work<br/>10 working days]
-    C --> D[Sprint Review<br/>2 hours]
-    D --> E[Sprint Retro<br/>1.5 hours]
+    A[Sprint Planning - 4 hours] --> B[Daily Standups - 15 min/day]
+    B --> C[Development Work - 10 working days]
+    C --> D[Sprint Review - 2 hours]
+    D --> E[Sprint Retro - 1.5 hours]
     E --> A
 
     style A fill:#e1f5ff

01-curriculum/06-quality-assurance.md

@@ -34,9 +34,9 @@ Quality isn't just QA's job - it's everyone's responsibility. This module teache
 
 ```mermaid
 graph TD
-    A[Manual/Exploratory<br/>5% of tests] --> B[UI/E2E Tests<br/>15% of tests]
-    B --> C[Integration Tests<br/>30% of tests]
-    C --> D[Unit Tests<br/>50% of tests]
+    A[Manual/Exploratory - 5% of tests] --> B[UI/E2E Tests - 15% of tests]
+    B --> C[Integration Tests - 30% of tests]
+    C --> D[Unit Tests - 50% of tests]
 
     style A fill:#ff6b6b
     style B fill:#ffd93d

01-curriculum/07-technical-fluency.md

@@ -561,9 +561,9 @@ sequenceDiagram
     participant Twilio as SMS Gateway (Twilio)
     participant User as Customer's Phone
 
-    App->>Twilio: POST /sms/send<br/>{to: "+1-555-123", message: "Booking confirmed"}
+    App->>Twilio: POST /sms/send - {to: "+1-555-123", message: "Booking confirmed"}
     Twilio->>User: SMS delivered
-    Twilio->>App: POST /webhooks/sms-status<br/>{status: "delivered", message_id: "SM123"}
+    Twilio->>App: POST /webhooks/sms-status - {status: "delivered", message_id: "SM123"}
     App->>App: Update booking record: sms_delivered = true
 ```
 

02-reserve-easy-project/01-discovery/opportunity-tree.md

@@ -25,22 +25,22 @@ Desired Outcome (North Star)
 
 ```mermaid
 graph TD
-    Outcome[Desired Outcome:<br/>Maximize completed bookings<br/>Revenue per restaurant]
+    Outcome[Desired Outcome: - Maximize completed bookings - Revenue per restaurant]
 
-    Outcome --> Opp1[Opportunity 1:<br/>Diners abandon booking flow<br/>20% drop-off]
-    Outcome --> Opp2[Opportunity 2:<br/>Restaurants lose revenue to no-shows<br/>30% no-show rate]
-    Outcome --> Opp3[Opportunity 3:<br/>Booking modifications are difficult<br/>15% cancellation rate]
+    Outcome --> Opp1[Opportunity 1: - Diners abandon booking flow - 20% drop-off]
+    Outcome --> Opp2[Opportunity 2: - Restaurants lose revenue to no-shows - 30% no-show rate]
+    Outcome --> Opp3[Opportunity 3: - Booking modifications are difficult - 15% cancellation rate]
 
-    Opp1 --> Sol1A[Solution: 60-second booking flow<br/>Pre-filled forms for returning users]
-    Opp1 --> Sol1B[Solution: Guest checkout<br/>No account required]
-    Opp1 --> Sol1C[Solution: Apple Pay / Google Pay<br/>One-tap payment]
+    Opp1 --> Sol1A[Solution: 60-second booking flow - Pre-filled forms for returning users]
+    Opp1 --> Sol1B[Solution: Guest checkout - No account required]
+    Opp1 --> Sol1C[Solution: Apple Pay / Google Pay - One-tap payment]
 
-    Opp2 --> Sol2A[Solution: Deposit system<br/>$10/person for parties 6+]
-    Opp2 --> Sol2B[Solution: 24-hour SMS reminder<br/>Reduce forgetfulness]
-    Opp2 --> Sol2C[Solution: Easy cancellation<br/>Free up tables for walk-ins]
+    Opp2 --> Sol2A[Solution: Deposit system - $10/person for parties 6+]
+    Opp2 --> Sol2B[Solution: 24-hour SMS reminder - Reduce forgetfulness]
+    Opp2 --> Sol2C[Solution: Easy cancellation - Free up tables for walk-ins]
 
-    Opp3 --> Sol3A[Solution: Self-serve modification<br/>Change time/party size in app]
-    Opp3 --> Sol3B[Solution: Flexible cancellation policy<br/>Full refund if >24 hours notice]
+    Opp3 --> Sol3A[Solution: Self-serve modification - Change time/party size in app]
+    Opp3 --> Sol3B[Solution: Flexible cancellation policy - Full refund if >24 hours notice]
 
     style Outcome fill:#e1f5ff,stroke:#0066cc,stroke-width:3px
     style Opp1 fill:#fff4e1,stroke:#ff9900,stroke-width:2px

02-reserve-easy-project/03-design/process-maps.md

@@ -36,7 +36,7 @@ sequenceDiagram
         D->>H: Provide name & phone number
         H->>B: Write booking manually
         H->>D: "See you then!" (verbal only)
-        Note over D: No confirmation<br/>Anxiety!
+        Note over D: No confirmation - Anxiety!
     else Table Not Available
         H->>D: "Sorry, fully booked"
         D->>P: Call next restaurant
@@ -93,9 +93,9 @@ sequenceDiagram
         RD-->>RD: New booking alert
     end
 
-    A-->>D: Confirmation page<br/>Code: ABC123
+    A-->>D: Confirmation page - Code: ABC123
 
-    Note over D: Instant proof of booking<br/>Peace of mind!
+    Note over D: Instant proof of booking - Peace of mind!
 ```
 
 **Improvements:**
@@ -113,27 +113,27 @@ sequenceDiagram
 
 ```mermaid
 flowchart TD
-    Start([Diner clicks<br/>'Cancel Reservation']) --> Check{When is<br/>the booking?}
+    Start([Diner clicks Cancel Reservation]) --> Check{When is the booking?}
 
-    Check -->|> 24 hours| FullRefund[Full refund<br/>if deposit paid]
-    Check -->|2-24 hours| PartialRefund[50% refund<br/>if deposit paid]
+    Check -->|> 24 hours| FullRefund[Full refund - if deposit paid]
+    Check -->|2-24 hours| PartialRefund[50% refund - if deposit paid]
     Check -->|< 2 hours| NoRefund[No refund]
 
-    FullRefund --> UpdateDB[Update booking<br/>status = 'cancelled']
+    FullRefund --> UpdateDB[Update booking status to cancelled]
     PartialRefund --> UpdateDB
     NoRefund --> UpdateDB
 
-    UpdateDB --> SendSMS[Send SMS<br/>'Cancellation confirmed']
-    SendSMS --> NotifyRestaurant[Notify restaurant<br/>via dashboard]
+    UpdateDB --> SendSMS[Send SMS Cancellation confirmed]
+    SendSMS --> NotifyRestaurant[Notify restaurant - via dashboard]
 
-    FullRefund --> ProcessRefund{Deposit<br/>paid?}
+    FullRefund --> ProcessRefund{Deposit - paid?}
     PartialRefund --> ProcessRefund
     NoRefund --> ProcessRefund
 
-    ProcessRefund -->|Yes| InitiateRefund[Stripe refund API<br/>3-5 business days]
+    ProcessRefund -->|Yes| InitiateRefund[Stripe refund API - 3-5 business days]
     ProcessRefund -->|No| Skip[Skip refund]
 
-    InitiateRefund --> End([Cancellation<br/>complete])
+    InitiateRefund --> End([Cancellation - complete])
     Skip --> End
     NotifyRestaurant --> End
 
@@ -159,8 +159,8 @@ stateDiagram-v2
     [*] --> Confirmed: Booking created
 
     Confirmed --> InProgress: Booking time arrives
-    InProgress --> Completed: Diner shows up<br/>(Host marks 'Seated')
-    InProgress --> NoShow: Diner doesn't arrive<br/>(15 min past booking time)
+    InProgress --> Completed: Diner shows up, Host marks Seated
+    InProgress --> NoShow: Diner doesnt arrive, 15 min past booking time
 
     Completed --> RefundDeposit: If deposit paid
     RefundDeposit --> [*]

02-reserve-easy-project/06-qa/test-cases/TC-001-guest-booking.md

@@ -53,9 +53,9 @@
 | 16   | Leave "Special Requests" field empty (optional)                                                                                                                                                                                                    | Field remains empty, no error                                          |
 | 17   | Click "Confirm Booking" button                                                                                                                                                                                                                     | Loading spinner appears for 1-3 seconds                                |
 | 18   | Wait for confirmation page to load                                                                                                                                                                                                                 | Confirmation page displays within 5 seconds                            |
-| 19   | Verify confirmation page content: <br/>- "Booking Confirmed!" heading<br/>- Restaurant name: "Bella Italia"<br/>- Date: Tomorrow's date<br/>- Time: 7:00 PM<br/>- Party size: 4<br/>- Confirmation code: 6-character alphanumeric (e.g., "XYZ123") | All details match booking inputs, confirmation code is displayed       |
+| 19   | Verify confirmation page content:  - - "Booking Confirmed!" heading - - Restaurant name: "Bella Italia" - - Date: Tomorrow's date - - Time: 7:00 PM - - Party size: 4 - - Confirmation code: 6-character alphanumeric (e.g., "XYZ123") | All details match booking inputs, confirmation code is displayed       |
 | 20   | Check phone +15551234567 for SMS                                                                                                                                                                                                                   | SMS received within 30 seconds                                         |
-| 21   | Verify SMS content:<br/>- Contains "Bella Italia"<br/>- Contains date and time<br/>- Contains party size "4"<br/>- Contains confirmation code<br/>- Contains link to modify/cancel                                                                 | All required information is present in SMS                             |
+| 21   | Verify SMS content: - - Contains "Bella Italia" - - Contains date and time - - Contains party size "4" - - Contains confirmation code - - Contains link to modify/cancel                                                                 | All required information is present in SMS                             |
 | 22   | Click link in SMS (optional)                                                                                                                                                                                                                       | Opens booking details page with Modify/Cancel options                  |
 
 ---

04-career-portfolio/pm-portfolio-guide.md

@@ -238,8 +238,8 @@ notion.so/yourname/product-portfolio
 
 ## Tools to Showcase in Portfolio
 
-| Category                | Tools to Mention                                   |
-| ----------------------- | -------------------------------------------------- |
+| Category          | Tools to Mention                                   |
+| ----------------- | -------------------------------------------------- |
 | **Analytics**     | SQL, Mixpanel, Amplitude, Google Analytics, Looker |
 | **Design**        | Figma (link mockups), Miro (link roadmaps)         |
 | **Project Mgmt**  | Jira, Linear, Asana                                |
@@ -264,8 +264,8 @@ notion.so/yourname/product-portfolio
 
 **Great PM Portfolios:**
 
-- [Lenny Rachitsky's Blog](https://www.lennysnewsletter.com) - PM best practices, case studies
-- [Jackie Bavaro's Portfolio](https://jackiebavaro.com) - Asana PM, clear case studies
+- [Lenny Rachitsky's Blog](https://www.lennysnewsletter.com) - PM best practices, case studies
+- [Jackie Bavaro's Portfolio](https://jackiebavaro.com) - Asana PM, clear case studies
 - [Ken Norton essays](https://www.bringthedonuts.com) - Google PM, thought leadership
 
 ---