Conversation
fredericsimard
approved these changes
Jul 17, 2025
Contributor
Author
|
Thank you both! @fredericsimard do you mind checking the JA version of the Schedule/Reference doc? there's a slight formatting error probably related to the SEO metadata at the top that I'm not sure how to adjust for this lang. 
Could you help me fix it? Thanks! |
Contributor
|
@Sergiodero Fixed! You can merge, commit added to this PR. |
Contributor
Author
|
Thanks @fredericsimard, merging now! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the following files in EN, FR, JA and ES to align with the latest changes in the google/transit repo:
Changes consist of:
I ran the site locally and formatting looks good for the most part except for the Ref document in Japanese, I think the SEO metadata is showing up at the top, do you mind taking a look and fixing it @fredericsimard? @skalexch As usual do you mind having a look at the FR? Thanks!