Repository navigation
Update Spanish translation for v1 removal - #915
Merged
Merged
Conversation
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
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.
Short Description
Updates the Spanish translation to match the v1 removal in #907, so the
espages no longer mention v1 or v2.Part of #905
Details
Brings 12 Spanish pages in line with the English changes on
drop-v1: removes the v1 note on Steps, the v1 cursors section, the v1/v2 wording in Planning, Portability versions, Standards, Try out, the HTTP to GoogleSheets tutorial and Troubleshooting, and the "v2⚡" title on Try out. Two pages (CLI walkthrough, What is OpenFn?) already matched the new English, so only their source hash changed.A separate review session found nothing to fix. The page with the most changes is Try out (
/es/documentation/get-started/try-out), if you want to spot-check one.AI Usage
Please disclose how you've used AI in this work (it's cool, we just want to know!):
You can read more details in our Responsible AI Policy