Moved Z<...> directives to avoid creating blank paragraphs

jonallen · Mar 23, 2011 · b05ea50 · b05ea50
1 parent 8baa134
commit b05ea50
Show file tree

Hide file tree

Showing 39 changed files with 39 additions and 117 deletions.
diff --git a/sections/accommodation_options.pod b/sections/accommodation_options.pod
@@ -1,8 +1,6 @@
 =head1 RESEARCH ACCOMMODATION OPTIONS
 
-Z<accommodation_options>
-
-Where are your attendees going to stay?
+Z<accommodation_options> Where are your attendees going to stay?
 
 While you are investigating your venue options, you should also bear in mind 
 what accommodation facilities are available nearby. If you are hosting the 

diff --git a/sections/accommodation_recommendations.pod b/sections/accommodation_recommendations.pod
@@ -1,8 +1,6 @@
 =head1 ACCOMMODATION
 
-Z<accommodation_recommendations>
-
-Everyone needs somewhere to stay. It's unlikely you are willing to have several 
+Z<accommodation_recommendations> Everyone needs somewhere to stay. It's unlikely you are willing to have several 
 hundred geeks living with you for a week, so you'll need to investigate at what 
 suitable accommodation is available.
 

diff --git a/sections/acknowledgements.pod b/sections/acknowledgements.pod
@@ -1,8 +1,6 @@
 =head1 Acknowledgments
 
-Z<acknowledgements>
-
-This book would not have been possible in its current form without questions,
+Z<acknowledgements> This book would not have been possible in its current form without questions,
 comments, suggestions, advice, wisdom, and encouragement from many, many
 people.  In particular, the author would like to thank:
 

diff --git a/sections/announcements.pod b/sections/announcements.pod
@@ -1,8 +1,6 @@
 =head1 ANNOUNCEMENTS
 
-Z<announcements>
-
-Throughout your preparations, you will need to plan when to make announcements. 
+Z<announcements> Throughout your preparations, you will need to plan when to make announcements. 
 There are some key milestones that need to be announced promptly, but it's also 
 important to remember to post newsletters and updates to the community early and 
 frequently, so that they know that the conference is still happening, and can 

diff --git a/sections/bid_prepare.pod b/sections/bid_prepare.pod
@@ -1,8 +1,6 @@
 =head1 PREPARE YOUR BID
 
-Z<bid_prepare>
-
-With your initial team assembled, research in progress and a budget outline, 
+Z<bid_prepare> With your initial team assembled, research in progress and a budget outline, 
 you're now in a position to begin preparing your bid proposal. Many bid 
 submissions from previous years are now online, so it is very worthwhile 
 reviewing these from the TPF or YEF sites. They will provide great examples of 

diff --git a/sections/budget_plan.pod b/sections/budget_plan.pod
@@ -1,8 +1,6 @@
 =head1 PLAN A BUDGET
 
-Z<budget_plan>
-
-Your budget is crucial. How much do you except your conference will cost? How 
+Z<budget_plan> Your budget is crucial. How much do you except your conference will cost? How 
 much sponsorship do you anticipate? How much do you expect to charge attendees? 
 How many paying attendees are you expecting? How many speakers are you expecting 
 to attend and for how many of them will you be paying for travel and/or 

diff --git a/sections/budget_progress.pod b/sections/budget_progress.pod
@@ -1,8 +1,6 @@
 =head1 YOUR BUDGET
 
-Z<budget_progress>
-
-From this point onwards your budget needs to be tightly controlled. You will 
+Z<budget_progress> From this point onwards your budget needs to be tightly controlled. You will 
 need to keep a handle on what costs are mounting up (paid and unpaid) and what 
 income you have coming in, as well as your targets to balance the books. If you 
 have a group member who is good with figures or has accounting or bookkeeping 

diff --git a/sections/call_for_papers.pod b/sections/call_for_papers.pod
@@ -1,8 +1,6 @@
 =head1 CALL FOR PAPERS
 
-Z<call_for_papers>
-
-The Call for Papers should be announced 4-6 months before the conference. This 
+Z<call_for_papers> The Call for Papers should be announced 4-6 months before the conference. This 
 gives speakers time to decide what talks they will submit. Give them at least a 
 month to respond, preferably longer. If you have decided on a conference theme, 
 announce that in the Call for Papers, as often speakers will write talks 

diff --git a/sections/call_for_registration.pod b/sections/call_for_registration.pod
@@ -1,8 +1,6 @@
 =head1 CALL FOR REGISTRATION
 
-Z<call_for_registration>
-
-Many attendees will attend the conference regardless of who will be speaking. 
+Z<call_for_registration> Many attendees will attend the conference regardless of who will be speaking. 
 Many speakers and attendees will simply be attending to meet with collaborators 
 on various projects. Others may need convincing. 
 

diff --git a/sections/conference_accessories.pod b/sections/conference_accessories.pod
@@ -1,8 +1,6 @@
 =head1 CONFERENCE ACCESSORIES
 
-Z<conference_accessories>
-
-While you're busy preparing funds, announcements and many other things, there 
+Z<conference_accessories> While you're busy preparing funds, announcements and many other things, there 
 are additional smaller items that will need to be prepared in advance. Many can 
 be very last minute, and as such are often good to get volunteers helping with.
 

diff --git a/sections/conference_events.pod b/sections/conference_events.pod
@@ -1,8 +1,6 @@
 =head1 CONFERENCE EVENTS
 
-Z<conference_events>
-
-The following are all activities that can take place during the conference. Some 
+Z<conference_events> The following are all activities that can take place during the conference. Some 
 are nice to have, so don't feel pressured to provide all of them.
 
 =head2 Day Trips & Partner Programmes

diff --git a/sections/conference_organisation.pod b/sections/conference_organisation.pod
@@ -1,10 +1,8 @@
 =head1 CONFERENCE ORGANISATION
 
-Z<conference_organisation>
-
 =head2 Pre-Registration & Registration
 
-It is always worthwhile opening up pre-registration the evening before the 
+Z<conference_organisation> It is always worthwhile opening up pre-registration the evening before the 
 conference. Many people will arrive early, and the more conference material you 
 can distribute before the day, the less time you'll be tied up registering 
 people on the first morning. Your time will be precious on the first morning, so 

diff --git a/sections/conference_pack.pod b/sections/conference_pack.pod
@@ -1,8 +1,6 @@
 =head1 THE CONFERENCE PACK
 
-Z<conference_pack>
-
-A conference pack for attendees at a large conference typically consists of the 
+Z<conference_pack> A conference pack for attendees at a large conference typically consists of the 
 proceedings, a writing implement, a writing pad, tshirt, badge and bag. A 
 smaller conference may have far less. All these and more are up for sponsorship. 
 Many sponsors are more than happy to provide pens, pads and other goodies to put 

diff --git a/sections/conference_schedule.pod b/sections/conference_schedule.pod
@@ -1,10 +1,8 @@
 =head1 THE CONFERENCE SCHEDULE
 
-Z<conference_schedule>
-
 =head2 Choosing Talks
 
-After the hard deadline for abstracts, you should allow your team at least a 
+Z<conference_schedule> After the hard deadline for abstracts, you should allow your team at least a 
 week to decide which talks to accept. Arrange a meeting with your team once 
 everyone has had a chance to read through the abstracts. You'll then be able to 
 make some quick choices as to what to accept and reject, hopefully making it a 

diff --git a/sections/conference_sessions.pod b/sections/conference_sessions.pod
@@ -1,8 +1,6 @@
 =head1 CONFERENCE SESSIONS
 
-Z<conference_sessions>
-
-=head2 Opening Address
+Z<conference_sessions> =head2 Opening Address
 
 You have a few responsibilities in your opening address:
 

diff --git a/sections/credits.pod b/sections/credits.pod
@@ -1,8 +1,6 @@
 =head1 CREDITS & ACKNOWLEDGEMENTS
 
-Z<credits>
-
-The original author of the YAPC.pm document, which was the original inspiration 
+Z<credits> The original author of the YAPC.pm document, which was the original inspiration 
 for this book, was Kevin A. Lenzo, the man who instigated the whole Perl 
 grassroots conference experience with the very first YAPC. Kevin released the 
 document to CPAN, alongside creating the Yet Another Society (YAS) organisation. 

diff --git a/sections/deadlines.pod b/sections/deadlines.pod
@@ -1,10 +1,8 @@
 =head1 FINAL DEADLINES
 
-Z<deadlines>
-
 =head2 Auction Items Deadline
 
-The auction (if you are holding one) comprises items donated by attendees and 
+Z<deadlines> The auction (if you are holding one) comprises items donated by attendees and 
 sponsors. Many publishers will be willing to provide books and other sponsors 
 may wish to donate items. It is important that you know about these early. You 
 should arrange to have these delivered to the organisers well in advance of the 

diff --git a/sections/first_11_years.pod b/sections/first_11_years.pod
@@ -1,10 +1,8 @@
 =head1 THE FIRST 11 YEARS
 
-Z<first_11_years>
-
 =head2 1999 - How It All Began
 
-The first Yet Another Perl Conference was held in Pittsburgh, PA at Carnegie 
+Z<first_11_years> The first Yet Another Perl Conference was held in Pittsburgh, PA at Carnegie 
 Mellon University in 1999, and had about 275 participants. The event was 
 attended by a small but mighty group of interested and interesting Perl people, 
 including Larry Wall, who delivered the opening keynote on the first day of the 

diff --git a/sections/mailing_lists.pod b/sections/mailing_lists.pod
@@ -1,8 +1,6 @@
 =head1 ORGANISATIONAL MAILING LISTS
 
-Z<mailing_lists>
-
-You should consider setting up at least two mailing lists.
+Z<mailing_lists> You should consider setting up at least two mailing lists.
 
 The first should be purely for the team of organisers, and should be a 
 completely closed list, where you can discuss ideas privately away from both the 

diff --git a/sections/other_events.pod b/sections/other_events.pod
@@ -1,8 +1,6 @@
 =head1 YAPCS, WORKSHOPS & HACKATHONS
 
-Z<other_events>
-
-Although the first YAPC was in 1999, ten years later in 2009 we now had 5 YAPC 
+Z<other_events> Although the first YAPC was in 1999, ten years later in 2009 we now had 5 YAPC 
 specific conferences (YAPC::NA, YAPC::Europe, YAPC::Asia, YAPC::Brazil and 
 YAPC::Russia), with OSDCs now also making their mark (Australia, Israel, 
 France).

diff --git a/sections/project_plan.pod b/sections/project_plan.pod
@@ -1,8 +1,6 @@
 =head1 PLAN YOUR PROJECT
 
-Z<project_plan>
-
-It cannot be emphasised enough how important a project plan is. A year before 
+Z<project_plan> It cannot be emphasised enough how important a project plan is. A year before 
 your event, you will need to start several task at once, and managing them 
 efficiently is a necessity. Organising a conference requires you to establish 
 priorities all the time, and having a project plan will better identify those 

diff --git a/sections/promotion.pod b/sections/promotion.pod
@@ -1,8 +1,6 @@
 =head1 PROMOTION
 
-Z<promotion>
-
-Six months before the event, possibly sooner, you need to start planning how you 
+Z<promotion> Six months before the event, possibly sooner, you need to start planning how you 
 are going to promote the event. Newsletters and announcements all need to appear 
 on your website, But you need to decide where else should you post them and 
 other updates?

diff --git a/sections/speakers_invite.pod b/sections/speakers_invite.pod
@@ -1,10 +1,8 @@
 =head1 INVITE SPEAKERS
 
-Z<speakers_invite>
-
 =head2 Invite Keynote Speakers
 
-Approach a few keynote speakers who you would like to invite. Based on your 
+Z<speakers_invite> Approach a few keynote speakers who you would like to invite. Based on your 
 budget, let them know whether you would be able to fund all or part of their 
 travel and accommodation expenses. If they or their company is able to fund 
 them, this will give you more flexibility for funding for the other speakers you 

diff --git a/sections/sponsorship.pod b/sections/sponsorship.pod
@@ -1,8 +1,6 @@
 =head1 FIND SPONSORS
 
-Z<sponsorship>
-
-Sponsorship is likely to be your biggest source of income for your event. While 
+Z<sponsorship> Sponsorship is likely to be your biggest source of income for your event. While 
 registration fees will cover a good portion of costs, you will need to find 
 sponsors both big and small to help cover the remaining costs.
 

diff --git a/sections/structure.pod b/sections/structure.pod
@@ -1,6 +1,4 @@
-=head1 Structure of This Book
-
-Z<structure>
+=head1 Structure of This Book Z<structure>
 
 =over 
 

diff --git a/sections/surveys.pod b/sections/surveys.pod
@@ -1,8 +1,6 @@
 =head1 YAPC CONFERENCE SURVEYS
 
-Z<surveys>
-
-The YAPC Conference Surveys started in 2006, and are now a regular feature of 
+Z<surveys> The YAPC Conference Surveys started in 2006, and are now a regular feature of 
 both YAPC::Europe and YAPC::NA. If you wish to provide a survey at your event, 
 you can contact surveys@yapc-surveys.org and request for an instance to be 
 set-up. There are two forms of surveys available, the talk evaluations and the 

diff --git a/sections/team_building.pod b/sections/team_building.pod
@@ -1,8 +1,6 @@
 =head1 ESTABLISH YOUR TEAM
 
-Z<team_building>
-
-No-one can organise a YAPC on their own. You don't need a big team, but many 
+Z<team_building> No-one can organise a YAPC on their own. You don't need a big team, but many 
 hands make light work :) While you may have a core team, you should look to 
 recruit others who can help with some of the smaller tasks. That's not 
 to say that you need 20 or so people. Most groups usually have two to four key 

diff --git a/sections/team_prepare.pod b/sections/team_prepare.pod
@@ -1,8 +1,6 @@
 =head1 PREPARE YOUR TEAM
 
-Z<team_prepare>
-
-You cannot organise this alone. While one day workshops might be possible for 
+Z<team_prepare> You cannot organise this alone. While one day workshops might be possible for 
 one person to handle, organizing a conference is very time consuming and 
 spreading the load enables the team to function better together and gets the 
 job done a lot quicker. Recruit local user group members, friends or colleagues 

diff --git a/sections/timeline1.pod b/sections/timeline1.pod
@@ -1,8 +1,6 @@
 =head1 TIMELINE 1 - THE BID
 
-Z<timeline1>
-
-Below are the main events in the conference bid life-cycle. Refer to this as 
+Z<timeline1> Below are the main events in the conference bid life-cycle. Refer to this as 
 you prepare your bid to keep yourself on track. The sections in this chapter 
 explain more fully the details of each step.
 

diff --git a/sections/timeline2.pod b/sections/timeline2.pod
@@ -1,8 +1,6 @@
 =head1 TIMELINE 2 - THE FOUNDATIONS
 
-Z<timeline2>
-
-Below are the main events in the first phase of the actual conference 
+Z<timeline2> Below are the main events in the first phase of the actual conference 
 preparation life-cycle. As before, refer to this as you prepare for the 
 conference to make sure you are on track and haven't missed anything.
 

diff --git a/sections/timeline3.pod b/sections/timeline3.pod
@@ -1,8 +1,6 @@
 =head1 TIMELINE 3 - THE FINAL PREPARATIONS
 
-Z<timeline3>
-
-Throughout the next six months your be busy with a lot of task behind the 
+Z<timeline3> Throughout the next six months your be busy with a lot of task behind the 
 scenes. However the tasks below are your more public tasks, which all have 
 significant timed announcements.
 

diff --git a/sections/timeline4.pod b/sections/timeline4.pod
@@ -1,8 +1,6 @@
 =head1 TIMELINE 4 - THE EVENT
 
-Z<timeline4>
-
-While not strictly a timeline, the following are all items you'll need to 
+Z<timeline4> While not strictly a timeline, the following are all items you'll need to 
 schedule and prepare for during the event, and make attendees aware of 
 throughout the event too.
 

diff --git a/sections/transport.pod b/sections/transport.pod
@@ -1,8 +1,6 @@
 =head1 REVIEW TRANSPORT FACILITIES
 
-Z<transport>
-
-How are you expecting the attendees to get to the conference and depart? Do you 
+Z<transport> How are you expecting the attendees to get to the conference and depart? Do you 
 have an international airport within easy reach of the city? If not, are there 
 adequate road or rail transport links from the airport to your town/city? Many 
 attendees may be travelling from abroad, and making them travel long distances 

diff --git a/sections/venue_booking.pod b/sections/venue_booking.pod
@@ -1,8 +1,6 @@
 =head1 BOOK THE VENUE
 
-Z<venue_booking>
-
-Ideally you should book your venue as soon as you have won the bid, but you will 
+Z<venue_booking> Ideally you should book your venue as soon as you have won the bid, but you will 
 need to sign some form of contract at least 6 months (preferably sooner) prior 
 to the start of the conference. Confirm dates with the venue and provide a 
 booking deposit, if you can, to secure the venue on the dates you require. Some 

diff --git a/sections/venue_committee.pod b/sections/venue_committee.pod
@@ -1,8 +1,6 @@
 =head1 THE VENUE COMMITTEE
 
-Z<venue_committee>
-
-The Venue Committee consists of previous organisers. So they all know what you 
+Z<venue_committee> The Venue Committee consists of previous organisers. So they all know what you 
 have ahead of you. While they know some of the pitfalls, they don't necessarily 
 know any you may face. However, they are there to help you. If you have any 
 questions, feel free to approach them at any time. Even months before you submit 

diff --git a/sections/venue_research.pod b/sections/venue_research.pod
@@ -1,8 +1,6 @@
 =head1 RESEARCH YOUR VENUE
 
-Z<venue_research>
-
-Before you think about anything to do with the organizing of an open source 
+Z<venue_research> Before you think about anything to do with the organizing of an open source 
 conference, there is one important thing you need to remember throughout. The
 conference is a means to bring together like minded souls, from all walks of 
 life, to meet and learn. "All walks of life" is what you need to remember. We 

diff --git a/sections/volunteers.pod b/sections/volunteers.pod
@@ -1,8 +1,6 @@
 =head1 RECRUITING VOLUNTEERS
 
-Z<volunteers>
-
-In the six months before your event you will have many small tasks that can be 
+Z<volunteers> In the six months before your event you will have many small tasks that can be 
 completed by someone outside of your core team. Recruit a local crew who are 
 willing help with fetching and carrying, and will act as volunteers and 
 timekeepers during the event too. 

diff --git a/sections/website_design.pod b/sections/website_design.pod
@@ -1,8 +1,6 @@
 =head1 DESIGN YOUR WEBSITE
 
-Z<website_design>
-
-You need an official site. This will be your primary focus point for 
+Z<website_design> You need an official site. This will be your primary focus point for 
 announcements and information about the conference, and will be used before, 
 during and after your event. It won't just be attendees and speakers that will 
 be viewing your website, but corporate managers and potential sponsors, so make 

diff --git a/sections/website_launch.pod b/sections/website_launch.pod
@@ -1,8 +1,6 @@
 =head1 LAUNCH YOUR WEBSITE
 
-Z<website_launch>
-
-If you haven't already done so, you will need to launch your website at least 
+Z<website_launch> If you haven't already done so, you will need to launch your website at least 
 six months before your conference. The website will be your primary method of 
 promoting the conference to sponsors, speakers, attendees and, perhaps most 
 importantly of all, to companies that will be sending their employees to your