[docsy] Move TAPs back under Community and copyedit (#95)

Author: chalin

content/en/community/_index.md

@@ -1,13 +1,8 @@
 ---
 title: Community
 menu: { main: { weight: 40 } }
-aliases: [/community]
-cascade:
-  type: docs
-# If your project has a local or external contributing page, then
-# specify the path or URL below.
+cascade: { type: docs }
 contributingUrl: https://github.com/theupdateframework/community
-# Content below, if any, will be added to the community page.
 ---
 
 {{% community-lists %}}

content/en/community/adoptions/index.md

@@ -1,8 +1,6 @@
 ---
 title: Adoptions
-weight: 40
-description: Explore practical adoptions of TUF
-liases: [/adoptions]
+aliases: [/adoptions]
 ---
 
 Each TUF adoption listed below links to an article, presentation, or repository

content/en/community/taps.md

@@ -0,0 +1,18 @@
+---
+title: TUF Augmentation Proposals
+LinkTitle: TAPs
+aliases: [/taps]
+---
+
+A TUF Augmentation Proposal (TAP) is a design document providing information to
+the TUF community, or describing a new feature for TUF or its processes or
+environment. We intend TAPs to be the primary mechanisms for proposing major new
+features, for collecting community input on an issue, and for documenting the
+design decisions that have gone into TUF.
+
+To review design changes that have been proposed to date, or to submit your own
+new feature, see the [TAPs GitHub repo]. For instructions on how to submit a
+TAP, see [TAP 1].
+
+[TAP 1]: https://github.com/theupdateframework/taps/blob/master/tap1.md
+[TAPs GitHub repo]: https://github.com/theupdateframework/taps