Minor dash typos in documentation

<td>Run PPP over USB.

<ul>

<li><code>&lt;tty&gt;</code> &mdash; the tty for PPP stream. For example <code>dev:/dev/omap_csmi_ttyl</code>. </li>

<li><code>[parm]... </code> &mdash zero or more PPP/PPPD options, such as <code>defaultroute</code>, <code>local</code>, <code>notty</code>, etc.</li></ul>

<li><code>[parm]... </code> &mdash; zero or more PPP/PPPD options, such as <code>defaultroute</code>, <code>local</code>, <code>notty</code>, etc.</li></ul>

<p>Note that you should not automatically start a PPP connection. </p></td>

<td></td>

<p>

The first, primary, purpose of this activity is to enable the user to 

interact with a single note &mdash to either {@code VIEW} the note or 

interact with a single note — to either {@code VIEW} the note or 

{@code EDIT} it.  (The {@code EDIT_NOTE} category is a synonym for 

{@code EDIT}.)  The intent would contain the URI for data matching the 

MIME type <code>vnd.android.cursor.item/vnd.google.note</code> &mdash;

The setting must be one of the values listed in the following table, or a 

combination of one "{@code state...}" value plus one "{@code adjust...}" 

value.  Setting multiple values in either group — multiple 

"{@code state...}" values, for example &mdash has undefined results.  

"{@code state...}" values, for example — has undefined results.  

Individual values are separated by a vertical bar ({@code |}).  For example:

</p>

constants for their columns.  For example, the 

{@link android.provider.Contacts.Phones android.provider.Contacts.Phones} class 

defines constants for the names of the columns in the phone table illustrated 

earlier &mdash {@code _ID}, {@code NUMBER}, {@code NUMBER_KEY}, {@code NAME},

earlier — {@code _ID}, {@code NUMBER}, {@code NUMBER_KEY}, {@code NAME},

and so on.</li>

<li><p>A filter detailing which rows to return, formatted as an SQL {@code WHERE}