Wherever possible, section headers should be identical to the ones in the article templates. Don't add a "Restaurants" header to an article; make it Eat instead. Don't add "Introduction", but rather Understand. The more consistent the names of article sections in Wikitravel are, the easier it is for readers to find what they're looking for.
Wiki markup has a specific format for section headers. Section headers should start with two equal signs. If there are sub-sections of the sections, their headers start with three equal signs, and sub-sub-sections get four equal signs, and so on up to the maximum number of equals signs which is six.
==Section 1== ===Section 1.1=== ===Section 1.2=== ====Section 1.2.1====
Section headers should be separated from text above with one blank line like this:
previous section had lots of text but that's all you need to know. ==Talk== The people of Frosnobish speak Frosnobian.
Section headers should follow the same rules of capitalisation as article titles: capitalise the first word in the title, and any proper names. Everything else should be lower case.
 Combining sections
When appropriate, two sections may be combined into one, such as See and do, or Eat and drink. Note that section names should still follow our standard conventions (eg: "See and do" is acceptable, "Sights and Sounds" is not), be capitalised according to our usual rules and the word "and" should be what separates the two section names.
Combining sections should only be done when it makes sense to do so; for instance, in Walt Disney World/Magic Kingdom, the line between attractions and activities is a difficult distinction for this destination, hence the combination of the See and Do sections made sense for this article.
 Which section to use
Use just one space to separate the ending punctuation mark of one sentence from the beginning of the next sentence.
(The MediaWiki software that Wikitravel uses will always display sentences separated by just one space, however many spaces you waste in your original text, so why not save a few bytes - they all add up!)
 See also