Center Airport Shuttle

,

, etc. Keep city/airport names and codes unchanged, i.e., "Terminal D", "Terminal E", "IAH", "United Airlines", "American Airlines", etc. Keep phone numbers and URLs unchanged (none present here). Return only the translated HTML. We need to translate "Terminal D — International carriers: Air France, British Airways, Emirates, KLM, Lufthansa, Turkish Airlines, Qatar, EVA, ANA, Singapore, Aeromexico, Volaris, and others. Transatlantic, Asia, and Gulf flights are almost always Terminal D." Also "Terminal E — United international (Latin America, Europe, Asia) plus select partner international operations." Then a paragraph: "From our historical IAH-bound trip data, the airline mix our customers fly is dominated by United Airlines (about 52% of IAH-bound trips — IAH is United’s largest hub), followed by American Airlines (about 13%), Delta (11%), Southwest (3%), and Alaska (3%). International is roughly 10% of volume, mostly British Airways, Emirates, Lufthansa, and Air Canada cross-border. Tell us your airline and flight number when you book and we’ll drop you at the correct upper-level departures curb — not the cell-phone lot, not the parking garage. On arrival trips we meet you curbside at lower-level arrivals after you have your bag." Then heading: "Vehicle Choice: Sedan, SUV, or Shuttle". We must translate all that text to natural Latin American Spanish, ensuring it reads as a native speaker would. Keep HTML tags. Keep the airline names unchanged (Air France, British Airways, etc.) Keep codes like IAH unchanged. We must also keep city/airport names and codes unchanged: "Terminal D", "Terminal E", "IAH", "United Airlines", "American Airlines", "Delta", "Southwest", "Alaska", "British Airways", "Emirates", "Lufthansa", "Air Canada". Keep phone numbers and URLs unchanged (none present). Also need to keep punctuation and dash etc. Use appropriate Spanish punctuation, e.g., dash (—) could be replaced by em dash (—) or use "—". The HTML includes — which is an em dash. Keep the same entity. Now translation. Must be careful about natural Spanish: Use "Terminal D" as is? Probably yes, as it's the name of the terminal. Use "Terminal D" unchanged. The rest we translate. Let's think about the translation: Original English:

Terminal D — International carriers: Air France, British Airways, Emirates, KLM, Lufthansa, Turkish Airlines, Qatar, EVA, ANA, Singapore, Aeromexico, Volaris, and others. Transatlantic, Asia, and Gulf flights are almost always Terminal D.

We can translate:

Terminal D — Aerolíneas internacionales: Air France, British Airways, Emirates, KLM, Lufthansa, Turkish Airlines, Qatar, EVA, ANA, Singapore, Aeromexico, Volaris y otras. Los vuelos transatlánticos, de Asia y del Golfo casi siempre salen del Terminal D.

But maybe we keep "International carriers" as "aerolíneas internacionales". The phrase "Transatlantic, Asia, and Gulf flights are almost always Terminal D." Could be "Los vuelos transatlánticos, de Asia y del Golfo casi siempre operan en el Terminal D." Something like that. Second item:

Terminal E — United international (Latin America, Europe, Asia) plus select partner international operations.

Translate:

Terminal E — Operaciones internacionales de United (Latinoamérica, Europa, Asia) más algunas operaciones internacionales de socios seleccionados.

Third part: paragraph. "From our historical IAH-bound trip data, the airline mix our customers fly is dominated by United Airlines (about 52% of IAH-bound trips — IAH is United’s largest hub), followed by American Airlines (about 13%), Delta (11%), Southwest (3%), and Alaska (3%). International is roughly 10% of volume, mostly British Airways, Emirates, Lufthansa, and Air Canada cross-border. Tell us your airline and flight number when you book and we’ll drop you at the correct upper-level departures curb — not the cell-phone lot, not the parking garage. On arrival trips we meet you curbside at lower-level arrivals after you have your bag." We need to translate this to Spanish. Let's do that. "Según nuestros datos históricos de viajes con destino a IAH, la combinación de aerolíneas de nuestros clientes está dominada por United Airlines (aproximadamente el 52% de los viajes con destino a IAH — IAH es el mayor hub de United), seguida de American Airlines (alrededor del 13%), Delta (11%), Southwest (3%) y Alaska (3%). El tráfico internacional representa aproximadamente el 10% del volumen, principalmente British Airways, Emirates, Lufthansa y Air Canada transfronterizas. Indíquenos su aerolínea y número de vuelo al hacer la reservación y lo dejaremos en la acera correcta de salidas del nivel superior — no en el lote de teléfonos celulares, no en el estacionamiento. En los viajes de llegada, lo esperamos en la acera de llegadas del nivel inferior después de que tenga su equipaje." But we need to ensure natural Latin American Spanish: "lote de teléfonos celulares" might be weird; perhaps "estacionamiento de celulares" or "lote de recogida de celulares"? However, the original phrase "cell-phone lot" refers to a waiting area for cellphones. In many airports, it's "celda de teléfonos" or "lote de celulares". Could be "lote de espera para celulares". Let's think: In US airports, "cell phone lot" is a parking area where people wait for arriving passengers. In Spanish, we can say "lote de celulares" or "estacionamiento de espera para celulares". The user wants "Keep phone numbers and URLs unchanged", not "cell-phone lot". So we need to translate the phrase "cell-phone lot" to Spanish but keep the concept. Possibly "lote de espera para celulares" or "zona de espera para celulares". But ensure it's natural for Latin American Spanish. Could be "lote de recogida de teléfonos". But perhaps we can simply translate as "lote de celulares". But we need to keep the sense. Also "parking garage" can be "estacionamiento". But "parking garage" is "garaje de estacionamiento". In many airports, "parking garage" is "estacionamiento". So we can say "no en el estacionamiento". However, the phrase "not the cell-phone lot, not the parking garage." could be "ni en el lote de celulares, ni en el estacionamiento". But we need to make it natural: "no en el lote de espera para celulares, ni en el estacionamiento". Use "ni" repeated. Or "no en el lote de celulares, tampoco en el estacionamiento". We'll decide. Now translation of "Upper-level departures curb" and "lower-level arrivals". "Upper-level departures curb" could be "la acera de salidas del nivel superior". "lower-level arrivals" as "la acera de llegadas del nivel inferior". That's okay. Now heading "Vehicle Choice: Sedan, SUV, or Shuttle". Translate: "Elección del vehículo: Sedán, SUV o Shuttle". However, "Shuttle" is often used in Spanish as "shuttle" (like "servicio de shuttle") but we could translate to "micros" or "servicio de enlace". But the user may want "Shuttle" unchanged as it's a brand? The user says keep city/airport names and codes unchanged, not specifically "Shuttle". The phrase "Vehicle Choice: Sedan, SUV, or Shuttle". Since "Shuttle" is a generic term for a shuttle service, we can translate as "Vehículo: Sedán, SUV o Shuttle". Or "Opción de vehículo: Sedán, SUV o Servicio de Shuttle". But maybe keep "Shuttle" unchanged because it's a proper noun for the type of service. But the user says keep city/airport names and codes unchanged. "Shuttle" is not a city/airport name or code, but the user may expect to keep it unchanged for consistency. Usually in Spanish translation you could leave "Shuttle" as is, or you could translate as "Servicio de transporte". The user says "Translate ... from English to NATURAL, native Latin American Spanish for travelers." So the translation should be natural Spanish. Using "Shuttle" may be unnatural; you could say "camioneta" or "micro". But typical phrase "Sedan, SUV, o Shuttle" is okay as many Spanish speakers use the English word "shuttle". It might be okay. But perhaps we should translate as "Sedán, SUV o servicio de shuttle". But we can also keep "Shuttle" unchanged. Let's decide. We must keep all HTML tags exactly as is. So We have a user request: "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 given HTML content (the paragraph and the h3 and the ul and li elements) into natural Latin American Spanish for travelers. We must keep all HTML tags exactly as is. That includes

, ,

,

,
• ,
  , etc. The user gave a snippet that contains only a few tags. We need to translate the English text inside those tags but keep tags unchanged, preserve attributes. Also keep city/airport names unchanged: "Center", "IAH", "Houston Airport System", "Terminal C", "Terminal E", "Terminal A", "TSA", "PreCheck", "CLEAR". Keep phone numbers and URLs unchanged. The snippet doesn't have any phone numbers or URLs. It does have "Houston Airport System site". Keep that unchanged. We must return only the translated HTML. Now we need to produce a natural Latin American Spanish translation that is idiomatic and uses a style suitable for travelers. Avoid overly formal or archaic forms; use "tú" perhaps. Use typical phrasing. Let's translate step by step. Original paragraph:

  For the Center-to-IAH route, the large majority of our trips are a four-door sedan (1–3 passengers, comfortable for the 3+ hour drive with two standard checked bags each). SUVs handle 4–6 passengers and up to a full set of bags per traveler. For groups of 7+ — family vacations, hunting parties heading to South Texas via IAH, corporate teams — we run a shuttle van (8–14 passengers) or a combined shuttle + SUV. All vehicles are late-model, climate-controlled, and professionally cleaned between trips; sedans and SUVs include bottled water and phone-charging cables, and the longer-haul shuttles include a USB port at every seat. Tell us your headcount and bag count when you book and we’ll size the vehicle correctly — quoting a sedan for 4 adults with bags is a setup for an uncomfortable 3+ hour ride and we’ll steer you toward an SUV.

  Need to translate into Spanish. We need to preserve HTML entities like – (en dash), — (em dash). We can replace them with appropriate Spanish punctuation, but better keep them as is. For Spanish, we may use "–" which is the same, but we can keep them. The translation must be natural Latin American Spanish. Use "tú" or "usted"? Typically for a service like a shuttle, using "tú" is friendly and informal. Use "nosotros" for we. Use "para" etc. The phrase "Center-to-IAH route" can be "ruta del Centro a IAH". Keep "IAH" unchanged. Let's translate: "Para la ruta del Centro a IAH, la gran mayoría de nuestros viajes se realizan en un sedán de cuatro puertas (1–3 pasajeros, cómodo para el viaje de más de 3 horas con dos maletas facturadas estándar por persona). Las SUVs acomodan de 4 a 6 pasajeros y hasta un juego completo de maletas por viajero. Para grupos de 7 o más — vacaciones familiares, partidas de caza que se dirigen al sur de Texas vía IAH, equipos corporativos — operamos una furgoneta de traslados (8–14 pasajeros) o una combinación de shuttle + SUV. Todos los vehículos son de modelos recientes, con control de clima y se limpian profesionalmente entre viajes; los sedanes y SUVs incluyen agua embotellada y cables de carga para teléfonos, y los shuttles de larga distancia incluyen un puerto USB en cada asiento. Dinos tu número de pasajeros y la cantidad de equipaje al reservar y ajustaremos el tamaño del vehículo correctamente — cotizar un sedán para 4 adultos con equipaje es una receta para un viaje incómodo de más de 3 horas y te recomendaremos una SUV." Now, need to keep the HTML tags:

  at start,

  at end, around "sedán de cuatro puertas". Also keep the – and — within text. Now the heading:

  Travel-Day Timing Tips for IAH

  Translate: "Consejos de tiempo para el día del viaje a IAH" or "Consejos de horario para el día del viaje a IAH". Keep "IAH". So:

  Consejos de horario para el día del viaje a IAH

  Or "Consejos de tiempo para el día del viaje a IAH". That is fine. Now the paragraph after heading:

  A few practical things we’ve learned shuttling East Texas travelers to IAH that are worth knowing before your trip:

  Translate: "Algunas cosas prácticas que hemos aprendido al trasladar viajeros del este de Texas a IAH que vale la pena conocer antes de tu viaje:" Now the list:
  • Security wait times. IAH posts live TSA wait times on the official Houston Airport System site. Terminal C and Terminal E security run the longest at peak; Terminal A is usually the fastest. Plan 30–45 minutes for security without PreCheck, 10–15 with PreCheck or CLEAR.
  We need to translate the bullet text. First part: "Security wait times." In Spanish: "Tiempos de espera de seguridad." Keep tags. Then: "IAH posts live TSA wait times on the official Houston Airport System site." Translate: "IAH publica los tiempos de espera actuales de TSA en el sitio oficial del Sistema Aeroportuario de Houston." Or "en el sitio oficial del Sistema Aeroportuario de Houston." Keep "Houston Airport System site". Actually the name "Houston Airport System site" can be left unchanged, but it's an English phrase. We can translate to Spanish but keep the proper noun "Houston Airport System". "el sitio oficial del Sistema Aeroportuario de Houston." That is fine. Then: "Terminal C and Terminal E security run the longest at peak; Terminal A is usually the fastest." Translate: "La seguridad en la Terminal C y la Terminal E suele ser la más lenta en horas pico; la Terminal A normalmente es la más rápida." Then: "Plan 30–45 minutes for security without PreCheck, 10–15 with PreCheck or CLEAR." Translate: "Calcula entre 30 y 45 minutos para la seguridad sin PreCheck, y entre 10 y 15 minutos con PreCheck o CLEAR." We need to keep the HTML tags:
• , . Also we need to keep – within the times. Now we need to preserve the HTML structure: The
  and
  • tags should be exactly as original. Now we need to ensure we didn't change any HTML attributes; there are none. Now we need to check that we didn't inadvertently change city/airport names and codes: "IAH", "Terminal C", "Terminal E", "Terminal A", "TSA", "PreCheck", "CLEAR", "Houston Airport System". We can keep them unchanged. We may keep "Houston Airport System site" unchanged. The phrase "Houston Airport System site" can remain as is. The user said keep city/airport names and codes unchanged. That includes the names. So it's okay to keep them in English. However, for natural Spanish, we might want to translate "site" to "sitio". But that would be a translation of the word "site", not a city or airport name. The instruction says keep city/airport names and codes unchanged. It does not forbid translating other words. So we can translate "site" to "sitio". However, we must keep the proper noun "Houston Airport System" unchanged. So we can say "en el sitio oficial del Sistema Aeroportuario de Houston". That keeps the name "Houston Airport System" unchanged? Actually we changed "Houston Airport System" to "Sistema Aeroportuario de Houston", which is a translation of the proper noun. That might violate the instruction to keep city/airport names unchanged. So better to keep "Houston Airport System" unchanged exactly as it appears. So we should not translate "Houston Airport System". Use the exact phrase "Houston Airport System". So: "en el sitio oficial del Houston Airport System". That is okay. Thus, bullet point translation:
  • Tiempos de espera de seguridad. IAH publica los tiempos de espera en vivo de TSA en el sitio oficial del Houston Airport System. La seguridad en la Terminal C y la Terminal E suele ser la más larga en horas pico; la Terminal A normalmente es la más rápida. Calcula entre 30–45 minutos para la seguridad sin PreCheck, 10–15 con PreCheck o CLEAR.
  Now the heading translation: "Travel-Day Timing Tips for IAH". We can translate to "Consejos de tiempo para el día del viaje a IAH". That is okay. Now final check: we must ensure we preserve all HTML tags exactly as-is:

  , ,

  ,

  ,
  • . Also preserve any attributes like class etc if present (none). Also preserve any special characters like – and —. Let's reconstruct the entire snippet. Original snippet:

    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." We need to translate the provided HTML snippet (some list items) into 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 do translation of the content, preserving HTML tags. Given the content is about IAH (George Bush Intercontinental Airport) and "Skyway / TerminaLink", "International connections", "Peak weeks", "Weather days". Need to translate to Latin American Spanish (like Mexico, Colombia, Argentina). Must be natural and not too literal. We need to preserve

  • tags and tags and   etc. Keep tags unchanged. The translation: Original English:
  • Skyway / TerminaLink. Once airside, IAH’s Skyway train and the TerminaLink underground train connect every terminal in 5–10 minutes. If you mis-clear at the wrong terminal it’s not a disaster — but starting at the right one saves 15+ minutes.
  • International connections. If your itinerary has you arriving at Terminal D or E from overseas and connecting domestic, plan a minimum 90-minute layover. CBP / immigration at IAH can be slow during the morning European-arrival bank (roughly 7–10 AM).
  • Peak weeks. Thanksgiving week, the last 10 days of December, spring break (mid-March), and Memorial Day weekend all run 1.5–2x normal volume at IAH. Add 30 minutes to your arrival buffer and book your Center pickup 48–72 hours ahead during these weeks.
  • Weather days. Gulf Coast thunderstorms and the rare ice event can ground-stop IAH. If your flight is delayed inbound to IAH, we automatically reshift your Center return pickup (we track tail numbers, not just scheduled times). For Center departures during a winter weather advisory along US-96 / US-59, we’ll reach out to discuss a safer pickup window or rebook to a same-day-later slot at no charge.
  We need to translate each piece. We need to keep city/airport names and codes unchanged: IAH, Terminal D/E, US-96/US-59. Also keep phone numbers and URLs unchanged (none present). Keep tags exactly as-is. Now translate to natural Latin American Spanish: First item: Skyway / TerminaLink. Once airside, IAH’s Skyway train and the TerminaLink underground train connect every terminal in 5–10 minutes. If you mis-clear at the wrong terminal it’s not a disaster — but starting at the right one saves 15+ minutes. In Spanish: "Skyway / TerminaLink." Might keep those proper nouns unchanged. Then "Una vez en la zona de embarque, el tren Skyway de IAH y el tren subterráneo TerminaLink conectan todas las terminales en 5 a 10 minutos. Si te confundes y bajas en la terminal equivocada, no es un desastre — pero comenzar en la correcta te ahorra más de 15 minutos." Better: "Skyway / TerminaLink." "Ya en el área de embarque, el tren Skyway y el tren subterráneo TerminaLink de IAH conectan todas las terminales en 5‑10 minutos. Si bajas en la terminal equivocada no es un desastre — pero comenzar en la correcta te ahorra más de 15 minutos." Make sure we preserve dash characters? The dash could be – for numbers, but it's okay. Keep – as is. So first list item:
  • Skyway / TerminaLink. Ya en la zona de embarque, el tren Skyway de IAH y el tren subterráneo TerminaLink conectan todas las terminales en 5–10 minutos. Si bajas en la terminal equivocada, no es un desastre — pero comenzar en la correcta te ahorra más de 15 minutos.
  Second item: "International connections." - "Conexiones internacionales." Keep strong. Content: "If your itinerary has you arriving at Terminal D or E from overseas and connecting domestic, plan a minimum 90-minute layover. CBP / immigration at IAH can be slow during the morning European-arrival bank (roughly 7–10 AM)." Translation: "Si tu itinerario te lleva a llegar a la Terminal D o E desde el extranjero y conectar con un vuelo doméstico, planifica al menos 90 minutos de escala. La inmigración / CBP en IAH puede ser lenta durante la ola de llegadas europeas por la mañana (aproximadamente de 7 a 10 AM)." We should keep "CBP" unchanged. Also keep dash – for 7–10. Thus:
  • Conexiones internacionales. Si tu itinerario te lleva a llegar a la Terminal D o E desde el extranjero y conectar con un vuelo doméstico, planifica al menos 90 minutos de escala. La inmigración / CBP en IAH puede ser lenta durante la ola de llegadas europeas por la mañana (aproximadamente de 7–10 AM).
  Third item: "Peak weeks." - "Semanas pico." Or "Semanas de alta demanda." Let's translate as "Semanas de mayor demanda." Content: "Thanksgiving week, the last 10 days of December, spring break (mid-March), and Memorial Day weekend all run 1.5–2x normal volume at IAH. Add 30 minutes to your arrival buffer and book your Center pickup 48–72 hours ahead during these weeks." Translation: "La semana de Acción de Gracias, los últimos 10 días de diciembre, las vacaciones de primavera (mediados de marzo) y el fin de semana del Día de los Caídos (Memorial Day) tienen entre 1,5 y 2 veces el volumen normal en IAH. Agrega 30 minutos a tu margen de llegada y reserva la recogida en el Centro entre 48 y 72 horas antes durante esas semanas." Need to keep numeric format as in original with –? The original had 1.5–2x (dash between numbers). In Spanish we might keep "1,5–2x" but it's okay to keep same "1.5–2x". For times "48–72". Keep as is. Thus:
  • Semanas de mayor demanda. La semana de Acción de Gracias, los últimos 10 días de diciembre, las vacaciones de primavera (mediados de marzo) y el fin de semana del Día de los Caídos (Memorial Day) tienen entre 1.5–2x el volumen normal en IAH. Agrega 30 minutos a tu margen de llegada y reserva la recogida en el Centro entre 48–72 horas antes durante esas semanas.
  Alternatively "Semanas pico". Might be more natural: "Semanas pico". But "Semanas de mayor demanda" seems good. Keep strong: Semanas pico. But original is "Peak weeks." Maybe translate as "Semanas pico". Could keep as "Semanas pico". It's more colloquial. "Semanas pico" is okay. But let's think: The translation should be natural Latin American Spanish for travelers. "Semanas pico" is used but might be considered a bit technical; "Semanas de alta temporada" could be better: "Semanas de alta temporada". Let's consider typical phrasing: "Semanas de mayor demanda" is fine. Now fourth item: "Weather days." - "Días de clima adverso." Or "Días de mal tiempo." Keep strong. Content: "Gulf Coast thunderstorms and the rare ice event can ground-stop IAH. If your flight is delayed inbound to IAH, we automatically reshift your Center return pickup (we track tail numbers, not just scheduled times). For Center departures during a winter weather advisory along US-96 / US-59, we’ll reach out to discuss a safer pickup window or rebook to a same-day-later slot at no charge." Translation: "Las tormentas eléctricas en la costa del Golfo y los raros eventos de hielo pueden provocar una paralización en tierra en IAH. Si tu vuelo llega con retraso a IAH, nosotros reprogramamos automáticamente la recogida de regreso en el Centro (rastreamos los números de cola, no solo los horarios programados). Para las salidas del Centro durante un aviso de clima invernal a lo largo de US-96 / US-59, nos pondremos en contacto para discutir una ventana de recogida más segura o reagendar a un horario posterior del mismo día sin costo." We need to keep "US-96 / US-59" unchanged. Keep ’ etc. Also we have — but in the original they used — for dash. We need to preserve. Original has — for dash and ’ for apostrophe in "we'll". In HTML: we need to keep as ’? The snippet: "we’ll reach out to discuss...". That is ’ apostrophe. Keep unchanged. Thus:
  • element describing cell-phone waiting lot; then closing

  (maybe earlier part of list), then an

  Shuttle vs. Drive-and-Park: The Real Math

  , then

  long paragraph, then

  Booking Window & Lead Time

  . We need to translate all English text to natural Latin American Spanish. Use appropriate vocabulary for travelers, e.g., "lote de espera para teléfonos celulares" or "estacionamiento para esperar llamadas", but keep as natural. Also preserve all HTML tags, so we must not modify any tags, just replace text content. Ensure we translate "Cell-phone waiting lot." to "Lote de espera para teléfonos celulares." etc. We need to ensure translation is natural Latin American Spanish, not overly formal, but accessible for travelers. We need to handle "IAH" and "JFK" are airport codes, they stay unchanged. Also "Beltway 8" and "Center" probably refer to a location: "Center" might be "Centro"? But "Center" is probably "Centro" but we might keep as "Center"? The user said keep city/airport names and codes unchanged. Does "Center" count as a city name? Probably not; it's a location name. The instruction: "Keep city/airport names and codes unchanged." So "Center" is not a city/airport name. But we might need to decide whether to translate "Center" to "Centro" or keep "Center". The phrase "a lot of Center travelers compare our shuttle to driving themselves and parking at IAH." "Center" might be the city "Center"? Possibly a place name: "Center". It could be a region near IAH. If we keep it unchanged, it's okay. However "Center" appears also in "Center-IAH". We might keep as "Center-IAH". That's okay. The user didn't specify to translate place names like "Center". But they said keep city/airport names unchanged. "Center" is ambiguous; maybe it's the city of "Center". It could be "Centro" in Spanish, but it's a proper name? The best is to keep "Center" unchanged to avoid confusion. The phrase "the official cell-phone lot off JFK Boulevard" stays unchanged as well. But "JFK Boulevard" may be a street name; should we keep unchanged? The user said "Keep city/airport names and codes unchanged." That doesn't mention street names, but to be safe we keep unchanged. Also "Houston curbside enforcement" maybe keep "Houston". That's a city name; keep unchanged. Also "$75–$150 ticket" remain same. "Texas tolls on Beltway 8" keep unchanged. "4-something a.m." keep unchanged. "red-eye" keep unchanged. "round-trip shuttle" maybe translate to "servicio de transporte compartido de ida y vuelta". But it's okay. Also "Booking Window & Lead Time" should be translated. Now translate the snippet. Original snippet:

  Cell-phone waiting lot. If a family member is meeting you at IAH, send them to the official cell-phone lot off JFK Boulevard — not the terminal curb. Houston curbside enforcement is strict and a $75–$150 ticket for circling is common.

  Shuttle vs. Drive-and-Park: The Real Math

  A lot of Center travelers compare our shuttle to driving themselves and parking at IAH. IAH’s terminal garages run about $24/day; Ecopark and Ecopark 2 (the official off-airport lots with free shuttle to the terminal) run about $7–$8/day; nearby private off-airport lots run $9–$12/day. For a 5-day trip, parking alone is $35–$120 — before the roughly 340 miles of round-trip gas (Center-IAH and back is about $45–$65 in fuel for most cars), Texas tolls on Beltway 8, the wear on your vehicle, and the 4-something a.m. drive back to Center after a red-eye. For week-plus trips or multi-passenger groups, our round-trip shuttle is usually the same total cost or less — and you skip the drive on both ends.

  Booking Window & Lead Time

  Now translation: We need to produce Spanish text. Start with
• Aviso de lote de espera para teléfonos celulares. Si un familiar viene a buscarte al IAH, envíalos al lote oficial de espera para celulares fuera del JFK Boulevard — no a la acera de la terminal. La aplicación de las normas de acera en Houston es estricta y una multa de $75–$150 por circular es común.

Then

Traslado frente a conducir y estacionar: la verdadera matemática

But we want natural Latin American Spanish: "Traslado frente a manejar y estacionar: la verdadera matemática" might be okay. Or "Comparativa entre shuttle y manejar y estacionar: la verdadera aritmética". But maybe better: "Shuttle frente a manejar y aparcar: el cálculo real". However we keep the word "Shuttle" maybe, as it's a term used. Better translation: "

Shuttle frente a conducir y estacionar: el cálculo real

" But maybe "Traslado frente a conducir y estacionar" is okay. The paragraph: need to translate entire paragraph.

Muchos viajeros del Center comparan nuestro shuttle con conducir ellos mismos y aparcar en IAH. Los estacionamientos de la terminal del IAH cuestan alrededor de $24/día; Ecopark y Ecopark 2 (los lotes oficiales fuera del aeropuerto con shuttle gratuito a la terminal) cuestan unos $7–$8/día; los lotes privados cercanos fuera del aeropuerto cuestan $9–$12/día. Para un viaje de 5 días, el solo estacionamiento es $35–$120 — antes de los aproximadamente 340 millas de gasolina de ida y vuelta (Center‑IAH y regreso consume unos $45–$65 en combustible para la mayoría de los autos), los peajes de Texas en Beltway 8, el desgaste de tu vehículo y la conducción de regreso al Center a eso de las 4 de la madrugada después de un vuelo nocturno. Para viajes de una semana o más o grupos con varios pasajeros, nuestro shuttle de ida y vuelta suele costar lo mismo o menos — y te ahorras la conducción en ambos extremos.

Then

Ventana de reserva y tiempo de anticipación

maybe translation of Booking Window & Lead Time: "Ventana de reservas y tiempo de anticipación". Better: "Periodo de reserva y tiempo de anticipación". The phrase "Booking Window & Lead Time" could be "Periodo de reserva y anticipación". Let's translate: "

Periodo de reserva y tiempo de anticipación

" or "

Ventana de reservas y tiempo de anticipación

" Both fine. Better: "

Ventana de reserva y tiempo de anticipación

" But maybe "Ventana de reserva y anticipación" is okay. We'll do: "

Ventana de reservas y tiempo de anticipación

" That sounds natural. Now we need to preserve all HTML tags exactly. For the

and

tags we must keep them as is. There's an opening
earlier not shown. But we have closing
after the
• . That remains unchanged. Now confirm any special characters: We have — (—) and – (–). Keep them as HTML entities. The translation should keep them unchanged. Now ensure the translation is natural Latin American Spanish. Avoid unnatural phrasing like "lote de espera para teléfonos celulares". In Latin America, "lote de espera para celulares" or "estacionamiento de espera para celulares". But we need to keep "Cell-phone waiting lot" translated. It's okay. Potential adjustments: "Cell-phone waiting lot." => "Lote de espera para celulares." That is natural. "official cell-phone lot off JFK Boulevard" => "lote oficial de espera para celulares fuera del JFK Boulevard". Good. "Houston curbside enforcement is strict and a $75–$150 ticket for circling is common." => "La aplicación de las normas de acera en Houston es estricta y una multa de $75–$150 por circular es común." Good. Now translation of the heading "Shuttle vs. Drive-and-Park: The Real Math". We could translate "Drive-and-Park" as "conducir y estacionar". "The Real Math" as "el cálculo real". So: "Shuttle frente a conducir y estacionar: el cálculo real". That's okay. Keep the word "Shuttle". Many Spanish speakers use "shuttle" in the travel industry. Paragraph translation: need to ensure correct use of Spanish for "$/day", "$/día". Should we keep the English "$24/day"? Usually keep as "$24/día". In Spanish we could keep "$24/día". The original uses "$24/day". We need to translate the HTML text (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 need to translate the content, which is in English, to Spanish (Latin American). Ensure translation is natural, native. Keep HTML tags as is. We need to translate the block:

  We accept bookings 24/7 online and by phone at (817) 403-6196. For the Center-to-IAH route, best fares are locked in 48–72 hours ahead of pickup — this is a long-haul ride and driver scheduling for Shelby County pickups has more variability than our short DFW-metro routes. Same-day bookings (down to about 4 hours before pickup) are usually accepted but subject to driver availability and may carry a small surge during peak windows. Round-trip bookings save 10% with promo code ONLINE, which on a Center-IAH round trip is typically a $40–$80 saving depending on vehicle size. Returning to Center from IAH is the same service in reverse — we meet you curbside at arrivals once you have your bag.