Terrell to Fort Worth Airport Shuttle Service
Book your Terrell to Fort Worth shuttle in two minutes — door-to-door, non-stop, 24/7. We pick up at any address in Terrell, TX and drop you curbside at Dallas/Fort Worth International Airport (DFW), or all the way into downtown Fort Worth. Fares start from $109 all-in — no surge pricing, no per-bag fees, and no hidden curbside surcharges.
Distance, Drive Time, and the Terrell → Fort Worth Corridor
How far is Terrell from Fort Worth, and how long is the drive?
Terrell sits in Kaufman County about 32 miles east of downtown Dallas on Interstate 20. Driving distance depends on where in “Fort Worth” you are headed:
- Terrell to DFW Airport — roughly 48–55 miles, door-to-curbside 60–90 minutes. This is where most Terrell→“Fort Worth” travelers actually need to go — DFW International sits on the Dallas/Fort Worth county line and is the official Fort Worth airport for nearly all commercial flights. We need to translate to natural Latin American Spanish for travelers. So we need to think about common phrasing that would be used by a traveler. Use "Terrell a Fort Worth", "Servicio de transporte", "Reserva", "precio", etc. Also keep HTML tags unchanged. Make sure to keep city/airport names unchanged (Terrell, Fort Worth, Dallas, DFW, etc.). Keep phone numbers and URLs unchanged; none present except URL for booking. Keep code exactly as is. We must preserve the HTML tags exactly as is, including — → etc. Use native Spanish phrasing. We need to consider punctuation; Spanish uses "¿" and "¡" but not necessary. Keep them as typical Spanish punctuation. Use proper Spanish characters (á, é, í, ó, ú, ñ). Keep original English words where needed: "door-to-door" could be "puerta a puerta" (or "de puerta a puerta"). "non-stop" could be "sin escalas". "24/7" remains "24/7". Keep "DFW". Keep "Interstate 20" as is. We need to translate "Book your Terrell to Fort Worth shuttle in two minutes". Could be "Reserva tu shuttle de Terrell a Fort Worth en dos minutos". "shuttle" maybe "servicio de transporte". "shuttle" is common to keep as "shuttle". Or "traslado". Many Spanish speakers use "shuttle" as is. We'll use "shuttle" or "servicio de shuttle". We could say "Reserva tu shuttle de Terrell a Fort Worth en dos minutos". That's okay. "door-to-door, non-stop, 24/7." Spanish: "de puerta a puerta, sin escalas, 24/7." Good. "We pick up at any address in Terrell, TX and drop you curbside at Dallas/Fort Worth International Airport (DFW), or all the way into downtown Fort Worth." Spanish: "Recogemos en cualquier dirección en Terrell, TX y te dejamos en la acera del Aeropuerto Internacional de Dallas/Fort Worth (DFW), o directamente en el centro de Fort Worth." Could also use "te dejamos en la acera" meaning curbside. "Fares start from $109 all-in — no surge pricing, no per-bag fees, and no hidden curbside surcharges." Spanish: "Las tarifas comienzan desde $109 todo incluido — sin precios por demanda, sin tarifas por equipaje adicional y sin suplementos ocultos en la acera." Then heading:
- , etc.
Make sure to keep the URL unchanged.
Also keep any special characters like → which is a right arrow. In Spanish translation, we might keep it unchanged.
Also need to ensure the entire output is just the HTML with translations.
Potential translation quality: Use natural Latin American Spanish (not overly formal Spain Spanish). Use "usted" maybe? The text uses informal "you". In Latin American Spanish, it's common to use "tú". The original text uses "you". Use "tú". However, in a service page, "usted" might be more formal. But we can keep it informal as "tú". The translation might be: "Recogemos en cualquier dirección..." etc.
Also "shuttle" might be left unchanged. It's common in Latin American.
We must ensure "door-to-door" is "de puerta a puerta". "non-stop" is "sin escalas". "24/7" remains. "all-in" is "todo incluido". "no surge pricing" could be "sin precios por demanda". "no per-bag fees" maybe "sin tarifas por equipaje adicional". "no hidden curbside surcharges" "sin suplementos ocultos en la acera".
Let's translate each piece carefully.
Original HTML:
Terrell to Fort Worth Airport Shuttle Service
Book your Terrell to Fort Worth shuttle in two minutes — door-to-door, non-stop, 24/7. We pick up at any address in Terrell, TX and drop you curbside at Dallas/Fort Worth International Airport (DFW), or all the way into downtown Fort Worth. Fares start from $109 all-in — no surge pricing, no per-bag fees, and no hidden curbside surcharges.
Distance, Drive Time, and the Terrell → Fort Worth Corridor
How far is Terrell from Fort Worth, and how long is the drive?
Terrell sits in Kaufman County about 32 miles east of downtown Dallas on Interstate 20. Driving distance depends on where in “Fort Worth” you are headed:
- Terrell to DFW Airport — roughly 48–55 miles, door-to-curbside 60–90 minutes. This is where most Terrell→“Fort Worth” travelers actually need to go — DFW International sits on the Dallas/Fort Worth county line and is the official Fort Worth airport for nearly all commercial flights.
Servicio de shuttle de Terrell al Aeropuerto de Fort Worth
- Terrell to downtown Fort Worth (Sundance Square, Stockyards, Dickies Arena, TCU) — roughly 65–75 miles, door-to-door 85–125 minutes depending on traffic.
- `, ``, `
- `, `
- Terrell to downtown Fort Worth (Sundance Square, Stockyards, Dickies Arena, TCU) — roughly 65–75 miles, door-to-door 85–125 minutes depending on traffic.
`. Keep them. Ensure that HTML entities like `–` remain unchanged (they represent dash). Keep line breaks as in original. The translation should be natural Spanish for travelers, Latin American Spanish (so not Spain Spanish). So use "aproximadamente", "dependiendo del tráfico". The phrase "roughly" -> "aproximadamente". "door-to-door" can be "de puerta a puerta". "depending on traffic" -> "según el tráfico". "The corridor we actually drive (all three options on the table in real time):" -> "El corredor que realmente recorremos (las tres opciones disponibles en tiempo real):" For each bullet point, translate the English description. First bullet: "the default fastest path for DFW Airport drops most days. Stays on free-flow highway from Terrell west to Mesquite, then north on LBJ around northeast Dallas to the south-side terminal entry." We need to translate. Something like: "la ruta más rápida por defecto para los drops al Aeropuerto DFW la mayoría de los días. Mantiene la autopista de flujo libre desde Terrell hacia el oeste hasta Mesquite, luego hacia el norte por LBJ alrededor del noreste de Dallas hasta la entrada de la terminal del lado sur." Second bullet: "the cleaner mid-day alternative when I-635 is congested. SH-360 runs the east side of Arlington/Grand Prairie straight up to DFW’s south toll plaza and is usually faster outside peak." -> "la alternativa más despejada a media jornada cuando la I-635 está congestionada. SH-360 corre por el lado este de Arlington/Grand Prairie directamente hacia la caseta de peaje sur del DFW y generalmente es más rápida fuera de las horas pico." Third bullet: "the routing for Sundance Square, the Stockyards, Dickies Arena, TCU/medical district, and the Will Rogers complex. Adds about 25–35 minutes vs the DFW Airport drop." -> "la ruta para Sundance Square, los Stockyards, el Dickies Arena, el distrito médico/TCU y el complejo Will Rogers. Añade aproximadamente entre 25 y 35 minutos en comparación con el drop al Aeropuerto DFW." We need to keep the HTML tags exactly as is. Ensure no stray characters. The entire snippet is:
The corridor we actually drive (all three options on the table in real time):
- I-20 West → I-635 North (LBJ) → SH-183 West → International Parkway (DFW) — the default fastest path for DFW Airport drops most days. Stays on free-flow highway from Terrell west to Mesquite, then north on LBJ around northeast Dallas to the south-side terminal entry.
- I-20 West → SH-360 North → International Parkway (DFW) — the cleaner mid-day alternative when I-635 is congested. SH-360 runs the east side of Arlington/Grand Prairie straight up to DFW’s south toll plaza and is usually faster outside peak.
- I-20 West → I-30 West (downtown Fort Worth) — the routing for Sundance Square, the Stockyards, Dickies Arena, TCU/medical district, and the Will Rogers complex. Adds about 25–35 minutes vs the DFW Airport drop.
- Terrell to downtown Fort Worth (Sundance Square, Stockyards, Dickies Arena, TCU) — roughly 65–75 miles, door-to-door 85–125 minutes depending on traffic. ` We need to translate "roughly", "door-to-door", "depending on traffic". So the translation could be: `
- De Terrell al centro de Fort Worth (Sundance Square, Stockyards, Dickies Arena, TCU) — aproximadamente 65–75 millas, de puerta a puerta 85–125 minutos según el tráfico. ` Note that we preserve HTML tags: `
- `, ``, etc. Use `—` as original. Now the paragraph after `
Distance, Drive Time, and the Terrell → Fort Worth Corridor
Could be: "Distancia, tiempo de manejo y el corredor Terrell → Fort Worth". But "Drive Time" maybe "tiempo de manejo" or "duración del viaje". Use "Distancia, tiempo de manejo y el corredor Terrell a Fort Worth". Keep arrow. Paragraph:How far is Terrell from Fort Worth, and how long is the drive?
Spanish: "¿A qué distancia está Terrell de Fort Worth y cuánto dura el viaje?" Use Spanish punctuation. Then: "Terrell sits in Kaufman County about 32 miles east of downtown Dallas on Interstate 20." Spanish: "Terrell se encuentra en el condado de Kaufman, a unas 32 millas al este del centro de Dallas, en la Interestatal 20." "Driving distance depends on where in “Fort Worth” you are headed:" Spanish: "La distancia de manejo depende de a dónde te dirijas en «Fort Worth»:" List item: "Terrell to DFW Airport — roughly 48–55 miles, door-to-curbside 60–90 minutes. This is where most Terrell→“Fort Worth” travelers actually need to go — DFW International sits on the Dallas/Fort Worth county line and is the official Fort Worth airport for nearly all commercial flights." Spanish: "Terrell al Aeropuerto DFW — aproximadamente 48–55 millas, de puerta a acera 60–90 minutos. Este es el destino de la mayoría de los viajeros Terrell→«Fort Worth» — el Aeropuerto Internacional DFW se encuentra en la línea condal entre Dallas y Fort Worth y es el aeropuerto oficial de Fort Worth para casi todos los vuelos comerciales." We need to preserve the HTML tags. Ensure we keep,
, , ,
, ,
The corridor we actually drive (all three options on the table in real time):
```
We must translate the English text into natural Latin American Spanish for travelers. Keep HTML tags unchanged, preserve city/airport names and codes unchanged (including "Terrell", "Fort Worth", "Sundance Square", "Stockyards", "Dickies Arena", "TCU", "DFW", "International Parkway", "I-20 West", "I-635 North (LBJ)", "SH-183 West", "SH-360 North", "I-30 West", "Will Rogers complex", "Arlington", "Grand Prairie", "Mesquite", "Dallas", etc.) Keep phone numbers and URLs unchanged. The snippet doesn't have any phone numbers or URLs, but there are references to roads and location names that must remain unchanged. For Spanish translation, we need to produce a natural translation, likely using "Desde Terrell hasta el centro de Fort Worth (Sundance Square, Stockyards, Dickies Arena, TCU)" etc. But keep names as they are: Terrell, Fort Worth, Sundance Square, Stockyards, Dickies Arena, TCU, DFW, etc.
We need to preserve the HTML tags exactly: `
The corridor we actually drive (all three options on the table in real time):
` Translate: `El corredor que realmente recorremos (las tres opciones disponibles en tiempo real):
` Then the `- ` with three `
- ` items. First `
- `: `
- I-20 West → I-635 North (LBJ) → SH-183 West → International Parkway (DFW) — the default fastest path for DFW
The user wants translation of HTML content from English to NATURAL, native Latin American Spanish for travelers. Keep all HTML tags exactly as-is. Keep city/airport names and codes unchanged. Keep phone numbers and URLs unchanged. Return ONLY the translated HTML.
We have a snippet of HTML: a paragraph and heading and some content. Must translate into natural Latin American Spanish, for a target audience of travelers. The content describes a shuttle service to DFW and pickup zones in Terrell and Greater Kaufman County. The translation should be natural, correct Spanish, for Latin American Spanish, possibly Mexican or generic.
We must preserve HTML tags exactly. So just replace the English text inside tags with Spanish equivalents. Keep tags like
,
, ,
- ,
- , etc. Keep codes like DFW, I-20, FM-148, etc. Keep ZIP codes as is. Keep "ZIP" maybe should stay "ZIP"? The user wants city/airport names and codes unchanged. So DFW, I-20, FM-148, etc. Keep numbers unchanged. Keep phone numbers and URLs unchanged.
Potential issues: "Our drivers run all three daily and pick the one that fits your pickup ZIP, your DFW terminal (or your downtown FW address), and live traffic." The translation should be natural. "Nuestros conductores realizan las tres corridas diarias y eligen la que se ajusta a tu código postal de recogida, tu terminal del DFW (o tu dirección en el centro de FW) y el tráfico en tiempo real." That seems natural. Keep "DFW" unchanged. "FW" maybe stands for Fort Worth. Should we keep "FW"? Might be "FW" unchanged. Or maybe "Fort Worth" in Spanish could be "Fort Worth". But the instruction: Keep city/airport names and codes unchanged. So "FW" is an abbreviation for city, keep unchanged.
"and live traffic" => "y el tráfico en tiempo real". Fine.
"We watch real-time conditions on I-20 through Mesquite (the 6–9 a.m. westbound commute and the 4–7 p.m. eastbound return both routinely add 15–25 minutes during peak)." The translation: "Observamos las condiciones en tiempo real en la I-20 a través de Mesquite (la vuelta de la mañana de 6 a 9 a.m. en dirección oeste y la vuelta de la tarde de 4 a 7 p.m. en dirección este suelen agregar de 15 a 25 minutos durante las horas pico)." Keep the dash/hyphen. Keep the times exactly? They include "6–9 a.m." which is HTML for 6–9 a.m. So we should preserve that HTML entity. We need to translate the text but preserve HTML tags. For the part inside parentheses: "the 6–9 a.m. westbound commute and the 4–7 p.m. eastbound return both routinely add 15–25 minutes during peak". In Spanish we can say "el recorrido de la mañana de 6 a 9 a.m. en dirección oeste y el regreso de la tarde de 4 a 7 p.m. en dirección este suelen agregar de 15 a 25 minutos durante las horas pico". The dash/hyphen can remain.
Better: "el tráfico de la mañana de 6 a 9 a.m. en dirección oeste y el regreso de la tarde de 4 a 7 p.m. en dirección este suelen agregar entre 15 y 25 minutos durante las horas pico." Use the same HTML entities: "6–9 a.m." and "4–7 p.m." We need to preserve those. Actually the HTML is: "6–9 a.m." and "4–7 p.m." So we keep them. The phrase "westbound" => "en dirección oeste". "eastbound" => "en dirección este". "both routinely add 15–25 minutes during peak" => "ambos suelen agregar entre 15 y 25 minutos durante las horas pico". Keep "15–25" as HTML. So final string: "Observamos las condiciones en tiempo real en la I-20 a través de Mesquite (el recorrido de la mañana de 6–9 a.m. en dirección oeste y el regreso de la tarde de 4–7 p.m. en dirección este suelen agregar entre 15–25 minutos durante las horas pico)."
Next:
Pickup Zones in Terrell and Greater Kaufman County
. Translate: "Zonas de recogida en Terrell y el área metropolitana del condado de Kaufman". Or "Zonas de recogida en Terrell y el Greater Kaufman County". Keep "Kaufman County" unchanged? The user said keep city/airport names unchanged. "Kaufman County" is a county name. Should keep unchanged. So maybe "Zonas de recogida en Terrell y el Greater Kaufman County". But "Greater" is English. Should we translate to "Mayor"? Probably keep as is: "Zonas de recogida en Terrell y Greater Kaufman County". That seems odd. Better: "Zonas de recogida en Terrell y el área metropolitana del Condado de Kaufman". But keep "Kaufman County" unchanged? The instruction says keep city/airport names and codes unchanged. So "Kaufman County" is a name, but we can translate "Greater" to "Mayor" if we want. But we need natural Latin American Spanish, maybe "Zonas de recogida en Terrell y el área de Kaufman County". But "Kaufman County" is a proper noun. Keep it unchanged. Could keep "Greater Kaufman County" as is. But it's English. The page is aimed at travelers; might be okay to keep it English. However, maybe we can translate "Greater" to "Mayor" but then "Kaufman County" stays English. But Spanish may use "Greater" as "Mayor". But I'm not sure. Given instructions: Keep city/airport names and codes unchanged. That likely means don't translate proper nouns like city names, airport codes. "Terrell" is a city, keep unchanged. "Kaufman County" is a county; can treat as name. "Greater Kaufman County" is not a city but an area; but it's an English phrase. The instruction is ambiguous. I'd keep it unchanged, as "Greater Kaufman County". SoZonas de recogida en Terrell y Greater Kaufman County
. That seems fine. Then next:Where in Terrell do you pick up?
. Translate: "¿En qué parte de Terrell se recoge?" or "¿Dónde en Terrell se recoge?" But "Where in Terrell do you pick up?" could be "¿En qué zona de Terrell se recoge?" But keep strong tag. So¿En qué zona de Terrell se recoge?
. Then next:Everywhere — we are a true door-to-door service. There is no central meet point and no requirement to drive to a park-and-ride. Common pickup areas:
. Translate: "En todas partes — somos un verdadero servicio de puerta a puerta. No hay un punto de encuentro central ni la necesidad de conducir a un estacionamiento de transferencia. Áreas comunes de recogida:" Keep the dash. But "park-and-ride" in Spanish maybe "estacionamiento de transferencia" or "parque y ride"? Probably "estacionamiento de transferencia". Could also be "parada de transferencia". But keep as "park-and-ride" unchanged? The instruction says keep city/airport names and codes unchanged. Not phone numbers or URLs. Not required to keep "park-and-ride". So we can translate to "estacionamiento de transferencia" which is a known concept: "parada de regreso"? I think "estacionamiento de transferencia" is okay. Better: "En todas partes — somos un verdadero servicio de puerta a puerta. No hay punto de encuentro central ni necesidad de conducir a un 'park-and-ride'." But we may preserve English phrase "park-and-ride". But translation to Spanish: "No hay punto de encuentro central ni necesidad de conducir a un 'park-and-ride'." Might be okay. But maybe better to translate as "estacionamiento de transferencia". I think the phrase "park-and-ride" is known internationally, but translation to Spanish may be "parqueo y viaje". However, the user wants natural Latin American Spanish, so maybe use "estacionamiento de transferencia" or "parqueo de intercambio". Let's use "estacionamiento de transferencia". So:En todas partes — somos un verdadero servicio de puerta a puerta. No hay punto de encuentro central ni necesidad de conducir a un estacionamiento de transferencia. Áreas comunes de recogida:
Then- list items:
- Downtown Terrell (ZIP 75160) — the historic Moore Avenue district, the Kaufman County offices, the residential streets between Frances and Adelaide, and the new infill around Ben Gill Park. We need to translate the description while preserving the strong tags and parentheses and dash. Keep "Downtown Terrell" unchanged? The phrase "Downtown Terrell" is a proper name. Keep unchanged. Keep "ZIP 75160". Keep dash and dash. So:
- Downtown Terrell (ZIP 75160) — el histórico distrito de Moore Avenue, The user asks: "Translate this airport-shuttle landing-page HTML from English to NATURAL, native Latin American Spanish for travelers. Keep ALL HTML tags exactly as-is. Keep city/airport names and codes unchanged. Keep phone numbers and URLs unchanged. Return ONLY the translated HTML." So they gave an HTML snippet: it's a list with
- , , etc. They want translation into natural Latin American Spanish (so maybe using common forms like "nosotros" or "ustedes", but it's about a shuttle service, so likely a friendly tone for travelers. Keep HTML tags exactly as they are. Keep city/airport names and codes unchanged: "West Terrell toward Forney", "ZIP 75161", "Travis Ranch, Heartland, and Gateway subdivisions along US-80 and FM-740", "I-20", "Holiday Inn Express Terrell", "Hampton Inn Terrell", "La Quinta Terrell", "Airbnb / VRBO rentals around downtown and Lake Tawakoni", "Kaufman County neighbors", "Forney", "Kaufman", "Crandall", "Mabank", "Kemp", "Cedar Creek Lake communities", "DFW Terminal Routing — A, B, C, D, or E", "DFW Airport", "Terminal A", "Terminal B", "American Airlines (most domestic departures)", "American Eagle regional and select American domestic". Keep those names unchanged. Also keep URLs unchanged. So the translation will have Spanish sentences but referencing those names unchanged.
We need to provide only the translated HTML, no extra commentary.
Thus we need to translate each English phrase into natural Latin American Spanish.
Given the HTML snippet is partially truncated; after the
- after the last list items, there may be a
- West Terrell toward Forney (ZIP 75161) — the rapidly growing Travis Ranch, Heartland, and Gateway subdivisions along US-80 and FM-740. Convenient to I-20 westbound.
- Hotels and short-term rentals — we frequently pick up at the Holiday Inn Express Terrell, Hampton Inn Terrell, La Quinta Terrell, and the Airbnb / VRBO rentals around downtown and Lake Tawakoni. Tell us the hotel name and we will meet you under the porte cochere.
- Kaufman County neighbors — we serve Forney (10 miles west), Kaufman, Crandall, Mabank, Kemp, and the Cedar Creek Lake communities on the same routing.
- Terminal A — American Airlines (most domestic departures)
- Terminal B — American Eagle regional and select American domestic ``` The snippet ends with incomplete list items. The user wants translation of everything. We need to produce translation in natural Latin American Spanish. We must keep HTML tags exactly as is, including the — entity, the , etc. We'll need to translate the sentences, but not the names/codes. We must maintain punctuation and perhaps the same HTML line breaks. Provide the same structure. The translation: First line:
- West Terrell toward Forney (ZIP 75161) — the rapidly growing Travis Ranch, Heartland, and Gateway subdivisions along US-80 and FM-740. Convenient to I-20 westbound. Spanish translation: "West Terrell hacia Forney (ZIP 75161) — las subdivisiones de rápido crecimiento Travis Ranch, Heartland y Gateway a lo largo de US-80 y FM-740. Conveniente hacia I-20 en dirección oeste." Alternatively, "West Terrell hacia Forney (ZIP 75161) – las subdivisiones en rápido crecimiento Travis Ranch, Heartland y Gateway a lo largo de US-80 y FM-740. Acceso fácil a la I-20 en sentido oeste." Something like that. Second line:
- Hotels and short-term rentals — we frequently pick up at the Holiday Inn Express Terrell, Hampton Inn Terrell, La Quinta Terrell, and the Airbnb / VRBO rentals around downtown and Lake Tawakoni. Tell us the hotel name and we will meet you under the porte cochere. Spanish: "Hoteles y alquileres a corto plazo — frecuentemente recogemos en el Holiday Inn Express Terrell, Hampton Inn Terrell, La Quinta Terrell, y en los alquileres de Airbnb / VRBO cerca del centro y del Lake Tawakoni. Indícanos el nombre del hotel y te esperamos bajo el pórtico de arrivals." Actually porte cochere is a covered entrance for vehicles, but we can translate as "el pórtico de entrada". But "porte cochere" is a term maybe they want keep as French phrase? Probably we can translate as "el pórtico". But keep phrase unchanged? The user says keep all HTML tags exactly as-is; they didn't say keep English text unchanged. So we can translate "porte cochere" into Spanish, maybe "el pórtico". But might be better to keep "porte cochere" as is? The phrase is in English, but we can translate. I think we can translate to "el pórtico de entrada" which is natural. Third line:
- Kaufman County neighbors — we serve Forney (10 miles west), Kaufman, Crandall, Mabank, Kemp, and the Cedar Creek Lake communities on the same routing. Spanish: "Vecinos del condado de Kaufman — servimos Forney (10 millas al oeste), Kaufman, Crandall, Mabank, Kemp y las comunidades del Cedar Creek Lake en la misma ruta." Now
- Terminal A — American Airlines (most domestic departures) Spanish: "
- Terminal A — American Airlines (la mayoría de los vuelos domésticos) " But we need to keep the English airline names unchanged, per user request to keep city/airport names and codes unchanged. The airline names "American Airlines" and "American Eagle" are names, keep them unchanged. So we only translate description. So "Terminal A — American Airlines (la mayoría de los vuelos domésticos)". Keep parentheses. Now
- Terminal B — American Eagle regional and select American domestic Spanish: "
- Terminal B — American Eagle regional y vuelos domésticos selectos de American." Alternatively: "American Eagle regional y algunos vuelos domésticos de American." We can keep as "American Eagle regional y vuelos domésticos selectos de American". Thus final HTML snippet. We need to preserve HTML tags exactly as is. So we need to output exactly the same tags with modifications inside text content. Ensure there are no stray spaces or missing tags. We also need to include the line breaks as in the original? Not necessary but it's fine. Provide HTML only. Now, note: The snippet originally includes "the rapidly growing Travis Ranch, Heartland, and Gateway subdivisions". That phrase "rapidly growing" might be better translated as "de rápido crecimiento". Keep "Travis Ranch, Heartland, and Gateway" unchanged. So "las subdivisiones de rápido crecimiento Travis Ranch, Heartland y Gateway". Also note that "subdivisions" is Spanish "subdivisiones" or "urbanizaciones". But keep as "subdivisiones" (makes sense). So translation: " The user wants translation of HTML page content from English to NATURAL, native Latin American Spanish for travelers. Must keep all HTML tags exactly as-is, keep city/airport names and codes unchanged, keep phone numbers and URLs unchanged. Return ONLY the translated HTML. We need to translate the HTML snippet provided. Let's read the snippet:
- Terminal C — American Airlines (additional domestic)
- Terminal D — international departures (American, British Airways, Lufthansa, Emirates, Qatar, JAL, Korean, Aeromexico, and most foreign carriers)
- Terminal E — non-American carriers: Delta, United, Spirit, Frontier, Southwest (limited), JetBlue, Alaska, Sun Country
- For 6–9 a.m. departures, the westbound I-20 commute through Mesquite and into south Dallas backs up heavily on weekdays. We pre-set your pickup with that buffer built in — you do not need to ask.
- For Terminal D international departures, add 15–20 minutes vs domestic for international security and immigration. We default to a 3-hour pre-departure pickup for international unless you tell us otherwise.
- For 4–7 p.m. inbound rides (DFW → Terrell), expect 90–120 minutes during peak eastbound. We factor it into your return ETA. We need to translate the content into natural Latin American Spanish, focusing on traveling context. Must preserve HTML tags. Also must preserve city/airport names and codes (e.g., Terrell, Fort Worth, DFW, I-20, Mesquite, Dallas). Keep phone numbers and URLs unchanged. Not needed in this snippet. Also keep special characters like — – as HTML entities. We need to translate each line: Terminal list, description for each terminal, the paragraph, the heading, the list items. Ensure natural Spanish. Possible translations: Terminal C — American Airlines (additional domestic). Could be: "Terminal C — American Airlines (adicional doméstica)". But "adicional doméstica" maybe unnatural. Could be "vuelos domésticos adicionales". Or "vuelos domésticos adicionales de American Airlines". Keep "Terminal C". "American Airlines" stays. So: "Terminal C — American Airlines (vuelos domésticos adicionales)". This is natural. Terminal D — international departures (American, British Airways, Lufthansa, Emirates, Qatar, JAL, Korean, Aeromexico, and most foreign carriers). Translate: "Terminal D — salidas internacionales (American, British Airways, Lufthansa, Emirates, Qatar, JAL, Korean, Aeromexico y la mayoría de las compañías aéreas extranjeras)". Or "la mayoría de las líneas aéreas extranjeras". Keep names unchanged. Terminal E — non-American carriers: Delta, United, Spirit, Frontier, Southwest (limited), JetBlue, Alaska, Sun Country. Translate: "Terminal E — líneas aéreas no estadounidenses: Delta, United, Spirit, Frontier, Southwest (limitado), JetBlue, Alaska, Sun Country". Or "transportistas no estadounidenses". Keep as is. Paragraph: "Tell us your flight number when you book and we route to the correct terminal automatically — no need to look it up yourself." Spanish: "Indíquenos su número de vuelo al hacer la reserva y lo encaminaremos automáticamente al terminal correcto — sin necesidad de buscarlo usted mismo." Heading: "
- and
- are already present. Also preserve the tags. Keep the spaces and entity codes.
Thus final HTML should be:
- Terminal C — American Airlines (vuelos domésticos adicionales)
- Terminal D — salidas internacionales (American, British Airways, Lufthansa, Emirates, Qatar, JAL, Korean, Aeromexico y la mayoría de las líneas aéreas extranjeras)
- Terminal E — líneas aéreas no estadounidenses: Delta, United, Spirit, Frontier, Southwest (limitado), JetBlue, Alaska, Sun Country
Indíquenos su número de vuelo al hacer la reserva y lo encaminaremos automáticamente al terminal correcto — sin necesidad de buscarlo usted mismo.
Consejos de viaje para Terrell → Fort Worth / DFW
- Para salidas entre las 6–9 a.m., el trayecto hacia el oeste por la I-20 a través de Mesquite hacia el sur de Dallas se congestiona bastante los días laborales. Nosotros programamos su recogida con ese margen incorporado — no necesita pedirlo.
- Para salidas internacionales del Terminal D, agregue 15–20 minutos respecto a los vuelos domésticos para los controles de seguridad e inmigración internacionales. Por defecto, programamos la recogida 3 horas antes de la salida internacional, a menos que nos indique lo contrario.
- Para trayectos de regreso entre las 4–7 p.m. (DFW → Terrell), espere entre 90–120 minutos en horas pico de tráfico hacia el este. Lo incluimos en el tiempo estimado de regreso.
- after heading and before first
- . In original snippet:
Travel Tips for Terrell → Fort Worth / DFW
- ...
Thus we must include
- after h3, before first
- . In my translation, I wrote
Consejos de viaje para Terrell → Fort Worth / DFW
- ... then
- items and close with
Tell us your flight number when you book and we route to the correct terminal automatically — no need to look it up yourself.
. I translated as "Indíquenos su número de vuelo al hacer la reserva y lo encaminaremos automáticamente al terminal correcto — sin necesidad de buscarlo usted mismo." Good. Now check if any words should be capitalized differently in Spanish. In Spanish, "Terminal" is capitalized only if it's part of proper name, but it's okay. Check the first - items: original had "Terminal C" — American Airlines (additional domestic)". I used "American Airlines (vuelos domésticos adicionales)". The translation "vuelos domésticos adicionales" seems appropriate. Could also be "vuelos domésticos adicionales de American Airlines". But we kept the name. It reads: "Terminal C — American Airlines (vuelos domésticos adicionales)". Good. Second
- : "Terminal D" — international departures (American, British Airways, Lufthansa We need to translate the HTML snippet from English to NATURAL, native Latin American Spanish for travelers. The user wants the translation only, no extra commentary, keep all HTML tags exactly as-is, keep city/airport names and codes unchanged, keep phone numbers and URLs unchanged. Return only the translated HTML. We need to translate each textual content inside
- elements and
. For each bullet: First
- : Original: "
- Major Fort Worth events — Cowboys home games (AT&T Stadium in Arlington), Stock Show & Rodeo (January, Will Rogers complex), Dickies Arena concerts, NASCAR weekends at Texas Motor Speedway, and TCU home football all ripple traffic across the I-30 / I-820 corridor. Book a little earlier on event days. " We need to translate "Major Fort Worth events —" plus rest. Use natural Latin American Spanish. Keep city/airport names and codes unchanged (Fort Worth, Cowboys, AT&T Stadium, Arlington, Stock Show & Rodeo (January, Will Rogers complex), Dickies Arena concerts, NASCAR weekends at Texas Motor Speedway, TCU home football, I-30 / I-820 corridor). So we keep those names unchanged. Also "Book a little earlier on event days." Should become something like "Reserve con un poco más de anticipación los días de eventos." Or "Es recomendable hacer la reserva con un poco más de anticipación los días de eventos." Second
- : Original: "
- Rangers and Cowboys home games (Arlington) — SH-360 and I-30 through Arlington get heavy 2–3 hours before kickoff/first pitch. We route around it via I-635/SH-183 when possible. " Translate: "Rangers and Cowboys home games (Arlington)" remain same. Then "SH-360 and I-30 through Arlington get heavy 2–3 hours before kickoff/first pitch. We route around it via I-635/SH-183 when possible." In Spanish: "SH-360 e I-30 a través de Arlington se congestionan entre 2 y 3 horas antes del saque inicial/primer lanzamiento. Nosotros Routamos alrededor de eso a través de I-635/SH-183 cuando es posible." But "Routamos" is not Spanish; we should say "Nosotros trazamos ruta alternativa por" or "Nosotros evitamos el tráfico usando". Or "Nosotros lo evitamos a través de I-635/SH-183 cuando es posible." So: "Nosotros lo evitamos a través de I-635/SH-183 cuando es posible." Or "Nosotros tomamos rutas alternativas por I-635/SH-183 cuando es posible." Third
- : Original: "
- Flight delays — if your inbound flight is delayed or rerouted, your pickup adjusts automatically. You do not need to call. Text or call the dispatcher number on your confirmation when you have your bags and we will meet you curbside. " Translate: "Si tu vuelo de llegada se retrasa o es reruteado, tu recogida se ajusta automáticamente. No necesitas llamar. Envía un mensaje o llama al número del despachador que aparece en tu confirmación cuando tengas tu equipaje y te esperamos en la acera." But preserve "dispatcher number on your confirmation" phrase maybe "número del despachador en tu confirmación". Use "curbside" as "la acera" or "el bordillo". Many Latin American Spanish would say "el bordillo". Use "nosotros te esperamos en la acera". That's fine. Fourth
- : Original: "
- Need Love Field (DAL) instead? Some travelers fly Southwest out of Dallas Love Field instead of DFW. We run that lane too — see our Terrell to Love Field service. " Translate: "Necesitas Love Field (DAL) en su lugar? Algunos viajeros vuelan con Southwest desde el Dallas Love Field en lugar de DFW. Nosotros también cubrimos esa ruta — consulta nuestro servicio de Terrell a Love Field." Or "También ofrecemos ese recorrido — consulta nuestro servicio de Terrell a Love Field." Now
- . In my translation, I wrote
- ...
Thus we must include
- tag that hasn't been closed. Actually the snippet includes:
```
Tell us your exact street address when you book and the driver will meet you at the curb at your scheduled pickup time. For lake-house and Airbnb pickups, leave a gate code or landmark in the booking comments and we will route accordingly.
DFW Terminal Routing — A, B, C, D, or E
DFW Airport has five active terminals, each with its own departures-level curb. We drop at the correct one based on your airline so you walk straight to bag-drop:
Tell us your exact street address when you book and the driver will meet you at the curb at your scheduled pickup time. For lake-house and Airbnb pickups, leave a gate code or landmark in the booking comments and we will route accordingly.
Spanish: "Indícanos tu dirección exacta de calle al hacer la reserva y el conductor te esperará en la acera a la hora de recogida programada. Para recogidas en casas junto al lago y Airbnb, deja un código de acceso o un punto de referencia en los comentarios de la reserva y planificaremos la ruta en consecuencia." NowDFW Terminal Routing — A, B, C, D, or E
Spanish: "Ruta de terminales del DFW — A, B, C, D o E" NowDFW Airport has five active terminals, each with its own departures-level curb. We drop at the correct one based on your airline so you walk straight to bag-drop:
Spanish: "El aeropuerto DFW tiene cinco terminales activas, cada una con su propia acera de salidas. Te dejamos en la terminal correcta según tu aerolinea para que vayas directo al registro de equipaje." Now- with
Tell us your flight number when you book and we route to the correct terminal automatically — no need to look it up yourself.
Travel Tips for Terrell → Fort Worth / DFW
Travel Tips for Terrell → Fort Worth / DFW
" Should be translated: "Consejos de viaje para Terrell → Fort Worth / DFW". Or "Consejos de viaje de Terrell a Fort Worth / DFW". The arrow is → which we preserve. List items: 1. "For 6–9 a.m. departures, the westbound I-20 commute through Mesquite and into south Dallas backs up heavily on weekdays. We pre-set your pickup with that buffer built in — you do not need to ask." Translate: "Para salidas entre las 6 y las 9 a.m., el trayecto hacia el oeste por la I-20 a través de Mesquite hacia el sur de Dallas se congestiona bastante los días laborales. Nosotros programamos su recogida con ese margen incorporado — no necesita pedirlo." 2. "For Terminal D international departures, add 15–20 minutes vs domestic for international security and immigration. We default to a 3-hour pre-departure pickup for international unless you tell us otherwise." Translate: "Para salidas internacionales del Terminal D, agregue 15–20 minutos respecto a los vuelos domésticos para los controles de seguridad e inmigración internacionales. Por defecto, programamos la recogida 3 horas antes de la salida internacional, a menos que nos indique lo contrario." 3. "For 4–7 p.m. inbound rides (DFW → Terrell), expect 90–120 minutes during peak eastbound. We factor it into your return ETA." Translate: "Para trayectos de regreso entre las 4 y las 7 p.m. (DFW → Terrell), espere entre 90–120 minutos en horas pico de tráfico hacia el este. Lo incluimos en el tiempo estimado de regreso." Make sure to preserve the HTML tags exactly as they appear. For instance,
Routes Related to Terrell
-> translate to Spanish: "Rutas relacionadas con Terrell" maybe. Keep as is. Now final output: include all HTML tags unchanged. Ensure proper Spanish characters (accent marks, ñ). Use proper HTML entities for em dashes: — remain same. Be careful with double quotes inside attributes, but they are unchanged. Now check each translation for naturalness and correctness. Let's write each translation. First bullet: Principales eventos en Fort Worth — Partidos locales de los Cowboys (AT&T Stadium en Arlington), Stock Show & Rodeo (enero, complejo Will Rogers), conciertos en Dickies Arena, fines de semana de NASCAR en Texas Motor Speedway y partidos de fútbol americano de TCU en casa generan tráfico en el corredor I-30 / I-820. Reserva con un poco más de anticipación los días de eventos. Check for consistency: Keep "Cowboys home games", "AT&T Stadium" unchanged. "Stock Show & Rodeo" unchanged. "Will Rogers complex" maybe keep as "complejo Will Rogers". "Dickies Arena concerts" unchanged. "NASCAR weekends at Texas Motor Speedway" unchanged. "TCU home football" unchanged. "I-30 / I-820 corridor" unchanged. Second bullet: Partidos de local de Rangers y Cowboys (Arlington) — SH-360 e I-30 a través de Arlington se congestionan entre 2 y 3 horas antes del saque inicial/primer lanzamiento. Nosotros evitamos el tráfico usando I-635/SH-183 cuando es posible. Alternatively "Nosotros evitamos la congestión por I-635/SH-183 cuando es posible." Fine. Third bullet: Retrasos de vuelos — Si tu vuelo de llegada se retrasa o es reruteado, tu recogida se ajusta automáticamente. No necesitas llamar. Envía un mensaje o llama al número del despachador que aparece en tu confirmación cuando tengas tu equipaje y te esperamos en la acera. Potential nuance: "text or call the dispatcher number on your confirmation" could be "Envía un mensaje o llama al número del despachador que aparece en tu confirmación." Good. Fourth bullet: ¿Necesitas Love Field (DAL) en su lugar? Algunos viajeros vuelan con Southwest desde Dallas Love Field en lugar de DFW. Nosotros también cubrimos esa ruta — consulta nuestro servicio de Terrell a Love Field. Check: Keep the anchor unchanged. Finally h3:Rutas relacionadas con Terrell
Now double-check for any HTML entities that need escaping: — should remain as — in output. In bullet 1, we have — after "Fort Worth". That's fine. In bullet 2 we have — after "Arlington". Keep as is. In bullet 4 we have — after "ruta". Keep as is. Now we must output only the translated HTML. Ensure we don't include extra whitespace that changes formatting. Keep everything exactly. Now assemble final output: - , etc. Keep codes like DFW, I-20, FM-148, etc. Keep ZIP codes as is. Keep "ZIP" maybe should stay "ZIP"? The user wants city/airport names and codes unchanged. So DFW, I-20, FM-148, etc. Keep numbers unchanged. Keep phone numbers and URLs unchanged.
Potential issues: "Our drivers run all three daily and pick the one that fits your pickup ZIP, your DFW terminal (or your downtown FW address), and live traffic." The translation should be natural. "Nuestros conductores realizan las tres corridas diarias y eligen la que se ajusta a tu código postal de recogida, tu terminal del DFW (o tu dirección en el centro de FW) y el tráfico en tiempo real." That seems natural. Keep "DFW" unchanged. "FW" maybe stands for Fort Worth. Should we keep "FW"? Might be "FW" unchanged. Or maybe "Fort Worth" in Spanish could be "Fort Worth". But the instruction: Keep city/airport names and codes unchanged. So "FW" is an abbreviation for city, keep unchanged.
"and live traffic" => "y el tráfico en tiempo real". Fine.
"We watch real-time conditions on I-20 through Mesquite (the 6–9 a.m. westbound commute and the 4–7 p.m. eastbound return both routinely add 15–25 minutes during peak)." The translation: "Observamos las condiciones en tiempo real en la I-20 a través de Mesquite (la vuelta de la mañana de 6 a 9 a.m. en dirección oeste y la vuelta de la tarde de 4 a 7 p.m. en dirección este suelen agregar de 15 a 25 minutos durante las horas pico)." Keep the dash/hyphen. Keep the times exactly? They include "6–9 a.m." which is HTML for 6–9 a.m. So we should preserve that HTML entity. We need to translate the text but preserve HTML tags. For the part inside parentheses: "the 6–9 a.m. westbound commute and the 4–7 p.m. eastbound return both routinely add 15–25 minutes during peak". In Spanish we can say "el recorrido de la mañana de 6 a 9 a.m. en dirección oeste y el regreso de la tarde de 4 a 7 p.m. en dirección este suelen agregar de 15 a 25 minutos durante las horas pico". The dash/hyphen can remain.
Better: "el tráfico de la mañana de 6 a 9 a.m. en dirección oeste y el regreso de la tarde de 4 a 7 p.m. en dirección este suelen agregar entre 15 y 25 minutos durante las horas pico." Use the same HTML entities: "6–9 a.m." and "4–7 p.m." We need to preserve those. Actually the HTML is: "6–9 a.m." and "4–7 p.m." So we keep them. The phrase "westbound" => "en dirección oeste". "eastbound" => "en dirección este". "both routinely add 15–25 minutes during peak" => "ambos suelen agregar entre 15 y 25 minutos durante las horas pico". Keep "15–25" as HTML. So final string: "Observamos las condiciones en tiempo real en la I-20 a través de Mesquite (el recorrido de la mañana de 6–9 a.m. en dirección oeste y el regreso de la tarde de 4–7 p.m. en dirección este suelen agregar entre 15–25 minutos durante las horas pico)."
Next:
- Principales eventos en Fort Worth — Partidos locales de los Cowboys (AT&T Stadium en Arlington), Stock Show & Rodeo (enero, complejo Will Rogers), conciertos en Dickies Arena, fines de semana de NASCAR en Texas Motor Speedway y partidos de fútbol americano de TCU en casa generan tráfico en el corredor I-30 / I-820. Reserva con un poco más de anticipación los días de eventos.
- Partidos de local de Rangers y Cowboys (Arlington) — SH-360 e I-30 a través de Arlington se congestionan entre 2 y 3 horas antes del saque inicial/primer lanzamiento. Nosotros evitamos el tráfico usando I-635/SH-183 cuando es posible.
- Retrasos de vuelos — Si tu vuelo de llegada se retrasa o es reruteado, tu recogida se ajusta automáticamente. No necesitas llamar. Envía un mensaje o llama al número del despachador que aparece en tu confirmación cuando tengas tu equipaje y te esperamos en la acera.
- ¿Necesitas Love Field (DAL) en su lugar? Algunos viajeros vuelan con Southwest desde Dallas Love Field en lugar de DFW. Nosotros también cubrimos esa ruta — consulta nuestro servicio de Terrell a Love Field.
Rutas relacionadas con Terrell
We need to keep the closing after the list? The snippet originally ends withRoutes Related to Terrell
. In our output we included The user asks: "Translate this airport-shuttle landing-page HTML from English to NATURAL, native Latin American Spanish for travelers. Keep ALL HTML tags exactly as-is. Keep city/airport names and codes unchanged. Keep phone numbers and URLs unchanged. Return ONLY the translated HTML." So we need to translate the English text inside HTML to Spanish (Latin American). Keep HTML tags unchanged. Keep city/airport names and codes unchanged: "Kaufman County", "Terrell", "DFW", "Dallas", "Love Field (DAL)", "DFW", "Fort Worth". Keep phone numbers unchanged: (817) 403-6196. Keep URLs unchanged. Return only the HTML. We need to produce natural Latin American Spanish. The original English text: "Need a different lane out of Kaufman County? See our companion route pages: Terrell to DFW Airport, Terrell to Dallas, Terrell to Love Field (DAL), and our DFW airport shuttle hub.
Ready to ride? Book your Terrell → Fort Worth shuttle online in under two minutes, or call (817) 403-6196 — we answer 8 a.m. to 6 p.m. CST and the booking system is live 24/7.
" We need to translate "Need a different lane out of Kaufman County? See our companion route pages:" - "Necesitas otra ruta desde el Condado de Kaufman? Consulta nuestras páginas de rutas complementarias:" Maybe "Necesitas otra salida desde el Condado de Kaufman?" But "lane" could be "ruta". "See our companion route pages" -> "Consulta nuestras páginas de rutas complementarias". Keep city names unchanged: "Kaufman County" we could keep as "Condado de Kaufman"? The requirement is to keep city/airport names and codes unchanged. Does that include "Kaufman County"? The instruction says "city/airport names and codes unchanged". Kaufman County is a county, not a city. Possibly keep as "Kaufman County". But the translation can incorporate the phrase "Condado de Kaufman" or keep "Kaufman County". The instruction: "Keep city/airport names and codes unchanged." It didn't say "county names". So we can translate "Kaufman County" as "Condado de Kaufman"? That's a translation. But the rule says keep city/airport names unchanged. That might apply only to city and airport names (e.g., "Terrell", "DFW", "Dallas", "Love Field (DAL)", "Fort Worth"). So we can translate "Kaufman County" into Spanish. Typically you'd say "Condado de Kaufman". That's okay. Now, the rest: "Terrell to DFW Airport" -> "Terrell a DFW Airport"? Actually keep the same: "Terrell a DFW Airport". Since it's a proper noun, might keep "Terrell to DFW Airport". In Spanish we can do "Terrell a DFW Airport". That keeps airport code unchanged. The anchor text is "Terrell to DFW Airport". So we need to translate anchor text? The anchor text is visible to user. We can translate "Terrell a DFW Airport". That seems natural. "Terrell to Dallas" -> "Terrell a Dallas". "Terrell to Love Field (DAL)" -> "Terrell a Love Field (DAL)". "DFW airport shuttle hub" -> "Centro de shuttles del aeropuerto DFW". That's okay. Then "Ready to ride?" -> "¿Listo para viajar?" or "¿Listo para abordar?" Maybe "Listo para viajar?" Good. Then "Book your Terrell → Fort Worth shuttle online" -> "Reserva tu shuttle de Terrell a Fort Worth en línea". Since we need to keep arrow → maybe preserve the same. The rest: "in under two minutes" -> "en menos de dos minutos". "or call" -> "o llama al". Keep phone number as "(817) 403-6196". Then "we answer 8 a.m. to 6 p.m. CST" -> "respondemos de 8 a.m. a 6 p.m. CST". Could be "de 8 a.m. a 6 p.m. hora del Centro". But keep "CST". Then "and the booking system is live 24/7." -> "y el sistema de reservas está disponible 24/7." Make sure to preserve HTML tags exactly, including → and and —. We need to ensure that HTML entities like are preserved. We'll keep them. Now ensure we keep the HTML tags:, anchor text, etc. We'll produce the Spanish translation. Potential final HTML:
¿Necesitas otra ruta desde el Condado de Kaufman? Consulta nuestras páginas de rutas complementarias: Terrell a DFW Airport, Terrell a Dallas, Terrell a Love Field (DAL), y nuestro centro de shuttles del aeropuerto DFW.
¿Listo para viajar? Reserva tu shuttle de Terrell → Fort Worth en línea en menos de dos minutos, o llama al (817) 403-6196 — respondemos de 8 a.m. a 6 p.m. CST y el sistema de reservas está disponible 24/7.
We need to ensure that the translation is natural and correct. Also keep the and — exactly. In the first paragraph, there is no inside, but we can keep them as is. Double-check: The original second paragraph has "call (817) 403-6196 — we answer 8 a.m. to 6 p.m. CST and the booking system is live 24/7." We have replaced "call" with "llama al". We keep the after (817). We keep — after the phone number. Then we have "respondemos de 8 a.m. a 6 p.m. CST y el sistema de reservas está disponible 24/7." Everything seems correct. Potential improvements: Use "Reserva tu shuttle de Terrell a Fort Worth en línea". Could also use "Reserva tu servicio de shuttle de Terrell a Fort Worth en línea". But fine. Make sure to maintain the arrow entity →. We can keep it. Now check each HTML tag exactly:...
pairs. ... tags. Keep attributes exactly as original: title attributes also need translation? Title attributes are used for tooltips, may be kept in English? The instruction didn't say to translate title attributes, but typical translation would also translate title attribute values. However, the title text appears in English originally. We can translate them as well, but keep them in Spanish to be consistent. But the instruction says "Keep ALL HTML tags exactly as-is." Does that include the attributes? The tags themselves are