docs: Europe team weeks are every two months, not monthly - #3663
docs: Europe team weeks are every two months, not monthly#3663marcklingen wants to merge 1 commit into
Conversation
The handbook principles page already described 3-5 days in Berlin every two months. Careers, about, perks, and the travel policy still said monthly; update them to match. Co-authored-by: Marc Klingen <marcklingen@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dosubot
Bot
added
size:S
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
@claude review |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Looks good — straightforward, mechanical copy update. Checked that all four files and the previously-unchanged pages (handbook/how-we-work/principles.mdx, handbook/how-we-work/remote.mdx) now consistently say "3-5 days every two months" with no stray "one week per month" mentions left in content/; confirmed no anchor links reference the renamed "Monthly Berlin week" heading.
Extended reasoning...
Overview
The diff is a pure copy/text change across four marketing and handbook MDX pages, updating the stated cadence of the Berlin office gathering from "one week per month" to "3-5 days every two months" and relabeling one H2 heading and its frontmatter description accordingly. No code, components, or logic are touched.
Security risks
None. This is static marketing/handbook prose with no user input, auth, or data handling involved.
Level of scrutiny
Low. This warrants a light-touch review: verify wording consistency across all pages that mention the policy, verify heading/anchor integrity, and verify no other pages were missed. I grepped the whole content/ tree for "one week per month" / "monthly" Berlin phrasing and for "3-5 days every two months" and confirmed all six relevant pages (the four changed ones plus principles.mdx and remote.mdx, which reference the same policy but were correctly left unchanged) are now mutually consistent. I also checked that the renamed heading ("Monthly Berlin week" → "Berlin week") has no anchor references elsewhere in the repo, so no broken deep links result.
Other factors
The bug-hunting system reported no findings, and the two candidate issues it separately flagged (about the "Berlin week" section still describing a full Monday–Friday on-site schedule) were already investigated and ruled out in this run — that phrasing describes the shared logistics of an on-site week and isn't inherently contradicted by "3-5 days" (not everyone need be present all five days), and no reviewer objection is outstanding. The change is small, self-contained, and low risk, so no further human review is strictly necessary, though the underlying "5-day week structure vs 3-5 days" framing nuance in the travel policy body text is a minor stylistic point rather than a factual inconsistency worth blocking on.
2 participants
The handbook principles page already said European teammates spend 3-5 days in Berlin every two months. Several public and handbook pages still said the team meets monthly.
This updates those remaining mentions so the site matches the current cadence:
/careers— European roles are now 3-5 days every two months in Berlin/about— hiring copy matches the same cadence/handbook/perks-and-pay— remote-first perk wording/handbook/tools-and-processes/travel-and-expense-policy— Berlin week policy and headingThe principles page (
/handbook/how-we-work/principles) was already accurate and is unchanged.Greptile Summary
Updates public careers, company, perks, and travel-policy content to consistently state that European team weeks in Berlin occur every two months rather than monthly.
Confidence Score: 5/5
The PR appears safe to merge.
The changes are internally consistent, preserve valid MDX structure and links, and introduce no identified behavioral, publishing, or security failures.
Reviews (1): Last reviewed commit: "docs: say Europe team weeks are every tw..." | Re-trigger Greptile