Fixes:Crypto
diff --git a/content/pages/crypto.md b/content/pages/crypto.md
index fc1aa54..608342c 100644
--- a/content/pages/crypto.md
+++ b/content/pages/crypto.md
@@ -124,26 +124,6 @@
<h2 id="faq">Frequently Asked Questions<a class="headerlink" href="#faq" title="Permanent link">¶</a></h2>
-- <a href="#faq-productname">What is the "PRODUCT NAME/MODEL #" for my product?</a>
-- <a href="#faq-manufacturer">What is the MANUFACTURER?</a>
-- <a href="#faq-notification">What is the NOTIFICATION?</a>
-- <a href="#faq-firstnotification">When is the first time a notification email must be sent?</a>
-- <a href="#faq-public">What are examples of when a crypto item is publicly accessible through ASF servers?¶</a>
-- <a href="#faq-publicemails">Are public contributions of crypto items to the mailing list, Jira or Bugzilla databases considered exports?</a>
-- <a href="#faq-previouslyexported">If we distribute previously exported crypto items, must we still qualify the same item for export?</a>
-- <a href="#faq-manyproducts">If the ASF distributes a particular crypto item within one product under the Section 742.15(b) publicly available exemption, must the same item requalify when distributed in a different ASF product?</a>
-- <a href="#faq-versions">If the ASF distributes/exports a crypto item after qualifying it under the Section 742.15(b) publicly available exemption, must the same product requalify for release of future versions?</a>
-- <a href="#faq-notificationurl">Where must the email's notification URL point to?</a>
-- <a href="#faq-additionalemails">If the notification URL never changes, when are additional notification emails required?</a>
-- <a href="#faq-infousers">Is there any BIS requirement to tell users and/or redistributors of our products about the crypto within our products?</a>
-- <a href="#faq-twocryptos">When exporting a product that is not only designed to use some third-party crypto item, but also includes the third-party crypto item, does this require two notifications or one notification with two manufacturers?</a>
-- <a href="#faq-nonasfsource">Can the ultimate link to the crypto item's source code point to a non-ASF web page?</a>
-- <a href="#faq-compilerswitch">What if the object/binary code being distributed was built with a particular compiler switch?</a>
-- <a href="#faq-binaryurl">Do we need to notify the BIS of the location of object/binary files?</a>
-- <a href="#faq-includedlibssl">If my project ships a binary that includes libssl/libcrypto, what notifications must be made?</a>
-- <a href="#faq-linkedtolibssl">If my project ships a binary that provides bindings to OpenSSL, but does not include its source or binaries, what notifications must be made?</a>
-- <a href="#faq-nonamerican">Why should I, who am not a U.S. citizen nor resident, be constrained by some U.S. law?</a>
-- <a href="#faq-digest">Do digest algorithms such as MD5 and SHA1 require notification?</a>
<h4 id="faq-productname">What is the "PRODUCT NAME/MODEL #" for my product?<a class="headerlink" href="#faq-productname" title="Permanent link">¶</a></h4>
The product name is the name of the ASF product (e.g. "Apache Foo"), even if the notification is being made about another manufacturer's cryptography included in the ASF product. Do not list the ASF product's version number.
