update for 1.3.0



Please find every text where is written: 


AOps/SOps/Managers


and replace it with:


HOps/AOps/SOps/Managers









Find:


<p>
  
  SOps are a "higher" level than AOps and have all the AOp privileges in 
  addition to some extra powers. As the founder, you are at a higher level 
  still and you have all the SOp and AOp privileges, plus some founder-only
  powers. There is no need to add yourself to the SOp or AOp
  lists. 
</p>




Change to:

	<p>
  
  SOps are a "higher" level than AOps and have all the AOp privileges in 
  addition to some extra powers. As the founder, you are at a higher level 
  still and you have all the SOp and AOp privileges, plus some founder-only
  powers. There is no need to add yourself to the SOp or AOp
  lists. HOPs have the lowest access level in the channel.
</p>















Find:




<p>

  It's beyond the scope of this guide to give help on how to use all the
  ChanServ powers that are granted to AOps and SOps. However, by each
  ability the appropriate help command is given; typing this while on IRC
  will provide more information.
</p>



Under this add:



<p>
  HOPs have the following powers:
</p>

	<list type="bullet">

	<item>

	<p>

    They are given ops (%) when they enter the channel; if for some reason
    they are in the channel without ops, they can get ChanServ to give
    them ops at any time.
    (
<command>/chanserv help op</command>
)
  
</p>
</item>

<item>

	<p>
	They can kick other users from the channel.
	</p>
</item>

	
<item>

	<p>
	They can change the topic of the channel.
	</p>
</item>
</list>















find:


<title>
Things to consider when giving op (@%) access privileges
</title>


change to:


<title>
Things to consider when giving op (@, %) access privileges
</title>






Find:


<title>How to add or remove Managers/SOps/AOps</title>


change to:


<title>How to add or remove Managers/SOps/AOps and HOPs</title>










Find:



	<line>
/chanserv AOp 
<param>#channel</param>
 list
</line>



Under this add:


<line>
/chanserv HOp 
<param>#channel</param>
 list
</line>







Find: (here its xlist!!!)



	<line>
/chanserv AOp 
<param>#channel</param>
 xlist
</line>


Under this add:



<line>
/chanserv HOp 
<param>#channel</param>
 xlist
</line>







find:


<title>Adding Managers/SOps or AOps</title>


Change to:


<title>Adding channel access</title>








Find:



<line>
/chanserv AOp 
<param>#channel</param>
 add 
<param>nick or mask</param> <param>[reason]</param>
</line>



Under this add:


<line>
/chanserv HOp 
<param>#channel</param>
 add 
<param>nick or mask</param> <param>[reason]</param>
</line>






Find:

<Removing Managers/SOps or AOps>


change to:


<title>Removing channel access</title>






Find:

<line>
/chanserv AOp 
<param>#channel</param>
 del 
<param>number or entry in list</param>
</line>


under this add:


<line>
/chanserv HOp 
<param>#channel</param>
 del 
<param>number or entry in list</param>
</line>










Find:


<title>
Advice on using address masks in your AOp/SOp or Manager lists
</title>


change to:


<title>
Advice on using address masks in your access list
</title>










Find:


<p>

  It's generally best to use nicknames, rather than address masks, in
  op(@) access lists. There are several reasons for this:
</p>


change to:


<p>

  It's generally best to use nicknames, rather than address masks, in
  op(@, %) access lists. There are several reasons for this:
</p>







find:



<p>

    You can always tell exactly who has AOps/SOps or Managers.
  
</p>



Change to:



<p>

    You can always tell exactly who has HOP/AOp/SOp or Manager access.
  
</p>





find:



<title>Problems with the wrong people getting AOps/SOps or Managers</title>



change to:


<title>Problems with the wrong people getting access</title>







Find:


<p>

  To discover why somebody has AOp/SOp or Manager privileges in a channel, you can
  use the ChanServ 
<command>why</command>


change to:


<p>

  To discover why somebody has HOp/AOp/SOp or Manager privileges in a channel, you can
  use the ChanServ 
<command>why</command>









find:


<p>

    Even when ChanServ manages a channel, it is possible that some people who are not AOps
	or SOps might get ops (@) in that channel. The main way this can happen is if an AOp gives
	them ops.
</p>




Change to:




<p>

    Even when ChanServ manages a channel, it is possible that some 
    people who are not HOPs, AOps or SOps might get ops (@,%) in that channel. The main way this can happen is if an AOp gives
	them ops.
</p>






Find:


<p>

    If you as channel founder or Manager and you do not want this to happen, you can enable the OPGUARD feature.
	When this feature is turned on, ChanServ will not allow people to have ops (@) on a channel
	(even temporarily) unless they are on the AOp/SOp/Manager list or are the founder. If somebody
	else is given ops, ChanServ will remove their ops immediately.
</p>


change to:


<p>

    If you as channel founder or Manager and you do not want this to happen, you can enable the OPGUARD feature.
	When this feature is turned on, ChanServ will not allow people to have 
	ops (@,%) on a channel
	(even temporarily) unless they are on the HOp/AOp/SOp/Manager list or are the founder. If somebody
	else is given ops, ChanServ will remove their ops immediately.
</p>







find:


<p>

  Managers/SOps and AOps are people you trust enough to give them some power on
  your channel. Among other things, this means that they will
  automatically be given ops (@) when they enter. Managers can change some of the channel's settings, can add or remove SOps/AOps and AKICKs (only trusted users can gain this access). SOps also have the
  ability to add and remove AOps and AKICKs (permanent bans from the
  channel), so you should be especially careful when making people SOps.
</p>



change to:



<p>

  Managers/SOps, AOps and HOps are people you trust enough to give them some power on
  your channel. Among other things, this means that they will
  automatically be given ops (@,%) when they enter. Managers can change 
  some of the channel's settings, can add or remove SOps/AOps/HOps and AKICKs (only trusted users can gain this access). SOps also have the
  ability to add and remove AOps, hOps and AKICKs (permanent bans from the
  channel), so you should be especially careful when making people SOps.
</p>







Find:


	<title>
If at a later date you need to remove an AOp or SOp or Manager from the channel
  list because they have proven untrustworthy, left IRC, or similar
</title>

	<p>
Type 

	<command>
/chanserv 
<param>AOp or SOp or Manager</param>
<param>#channel</param>
 
  list
</command>
. When you find the entry for that person, you should note the 
  number and type 

	<command>
/chanserv 
<param>AOp or SOp or Manager</param>
<param>#channel</param>
 
  del 
<param>number</param>
</command>




change to:




	<title>
If at a later date you need to remove an HOp, AOp, SOp or Manager from the channel
  list because they have proven untrustworthy, left IRC, or similar
</title>

	<p>
Type 

	<command>
/chanserv 
<param>HOp or AOp or SOp or Manager</param>
<param>#channel</param>
 
  list
</command>
. When you find the entry for that person, you should note the 
  number and type 

	<command>
/chanserv 
<param>HOp or AOp or SOp or Manager</param>
<param>#channel</param>
 
  del 
<param>number</param>
</command>