How do I make org mode not interpret a line that begins with an asterisk as a headline? I have some verbatim text in my org mode document. Some of the lines begin with an asterisk. Org mode interprets these lines as headlines. I don't want that.
Here is the text with some context:
    * 20160721 Headline for July 21, 2016
    I created a git repository for rfc-tools.  It's in
    ~/Documents/rfc-tools.
    Renamed grep-rfc-index.sh to search-rfc-index.sh because it searches.
    That it uses grep is irrelevant.
    Wrote a README.md for the project.  Here it is:
    #+BEGIN_SRC text
    ----- BEGIN QUOTED TEXT -----
    This is the README.md for rfc-tools, a collection of programs for
    processing IETF RFCs.
    * fetch-rfcs-by-title.sh downloads into the current directory the RFCs
      whose titles contain the string given on the command line.  Uses an
      rfc-index file in the current directory.  Prefers the PDF version of
      RFCs but will obtain the text version if the PDF is not available.
    * fetch-sip-rfcs.sh downloads RFCs that contain "Session Initiation"
      in their titles into the current directory.
    * search-rfc-index.sh searches an rfc-index file in the current
      directory for the string given on the command line.  The string can
      contain spaces.
    * join-titles.awk turns the contents of an rfc-index file into a
      series of long lines.  Each line begins with the RFC number, then a
      space, then the rest of the entry from the rfc-index.
    ----- END QUOTED TEXT -----
    #+END_SRC
I want the lines between "----- BEGIN QUOTED TEXT -----" and "----- END QUOTED TEXT -----" to be plain text and subordinate to the headline "20160721 Headline for July 21, 2016". Org mode interprets all lines that begin with an asterisk as top-level headlines.
By the way, the verbatim text is Markdown. I hope that doesn't matter.
worked for me:
    #+BEGIN_SRC markdown
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With