Commit 1418d490 authored by Cynthia "Arty" Ng's avatar Cynthia "Arty" Ng 💬 Committed by Jamie Allen
Browse files

Fix broken links

parent c8513361

assets/includes/engineering/master-prioritization-list.md

+1 −1
Original line number Diff line number Diff line
@@ -3,7 +3,7 @@ 
| 1* | <a href="/handbook/security/#severity-and-priority-labels-on-security-issues">Security</a> | `bug::vulnerability` |

| 2* | Data Loss | `data loss` |

| 3* | Resilience, Reliability, <a href="/handbook/engineering/performance/index.html#availability">Availability</a>, <a href="/handbook/engineering/workflow/#infradev">and Performance</a>| `availability`, `infradev`, `Corrective Action`, `bug::performance` |

| 4 | <a href="/handbook/product/product-okrs/">OKR's</a> | |

| 4 | <a href="/handbook/product/product-processes/product-okrs/">OKR's</a> | |

| 5 | Usability | `Usability benchmark`, `SUS::Impacting`, `Deferred UX` |

| 6 | Instrumentation | `instrumentation` |

| 7 | xMAU / ARR Drivers | `direction` |

assets/includes/joint-r-d-okr-process.md

+1 −1
Original line number Diff line number Diff line
@@ -26,7 +26,7 @@ The OKR process is designed to tie in to the overall [OKR process](/handbook/com 
  - Teams have a chance to iterate as needed until the Key Review deadline (one week prior to the Key Review)

  - Product Program Management finalizes R&D OKRs in GitLab and mentions `@gl-product-pm` (section, stage, and group product leads), `@gitlab-com/engineering-division/cto-leadership`, and/or post in the #product and #engineering-fyi Slack channels to finalize KR drafts with their respective Quad

  - Leads from each section, stage, and group review R&D OKRs and provide feedback directly in GitLab on changes that may be needed.

  - Leads plan and propose their respective section, stage and section OKRs following the guidance on [how to write OKRs](/handbook/product/product-okrs/#how-to-write-okrs).

  - Leads plan and propose their respective section, stage and section OKRs following the guidance on [how to write OKRs](/handbook/company/okrs/okrs-basics/#how-to-write-okrs).

- **1 week** prior to key review meeting:

  - OKRs finalized and included in Key Review content (async)

- **Ongoing** after the key review meeting:

assets/includes/master-prioritization-list.md

+1 −1
Original line number Diff line number Diff line
@@ -3,7 +3,7 @@ 
| 1* | <a href="/handbook/security/engaging-with-security/#severity-and-priority-labels-on-security-issues">Security</a> | `bug::vulnerability` |

| 2* | Data Loss | `data loss` |

| 3* | Resilience, Reliability, <a href="/handbook/engineering/performance/index.html#availability">Availability</a>, <a href="/handbook/engineering/workflow/#infradev">and Performance</a>| `availability`, `infradev`, `Corrective Action`, `bug::performance` |

| 4 | <a href="/handbook/product/product-okrs/">OKR's</a> | |

| 4 | <a href="/handbook/product/product-processes/product-okrs/">OKR's</a> | |

| 5 | Usability | `Usability benchmark`, `SUS::Impacting`, `Deferred UX` |

| 6 | Instrumentation | `instrumentation` |

| 7 | xMAU / ARR Drivers | `direction` |

content/handbook/about/style-guide.md

+1 −1
Original line number Diff line number Diff line
@@ -6,7 +6,7 @@ GitLab's general communications practices are detailed at [GitLab Communication] 
See the [list of resources below](#related-resources) for links to other guides.



Handbook style guidance is covered primarily by [the handbook markdown guide](https://handbook.gitlab.com/docs/markdown-guide/),

and [the editing handbook page](../editing-handbook/_index.md#naming-pages-and-folder-structure).

and [the editing handbook page](editing-handbook/_index.md#naming-pages-and-folder-structure).



In the absence of handbook-specific guidance, follow:

content/handbook/business-technology/tech-stack-guide/index.md

+1 −1
Original line number Diff line number Diff line
@@ -195,4 +195,4 @@ Zuora Data to [Snowflake Enterprise Data Warehouse](/handbook/enterprise-data/pl 


#### Zuora to NetSuite



Zuora Revenue data is synced to NetSuite using the [Zuora Revenue to NetSuite Integration](/handbook/business-technology/enterprise-applications/integrations/wiki/integrations-list/zuora-revenue-to-netsuite/).
 
Zuora Revenue data is synced to NetSuite using the [Zuora Revenue to NetSuite Integration](https://gitlab.com/gitlab-com/business-technology/enterprise-apps/integrations/platypus/-/wikis/Integrations/Zuora-Revenue-to-Netsuite).