docs: update docs

1 files changed, 6 insertions, 6 deletions

diff --git a/docs/design/part-meta.txt b/docs/design/part-meta.txt
index 9fd576ec19..3ea6a3e2c0 100644
--- a/docs/design/part-meta.txt
+++ b/docs/design/part-meta.txt
@@ -120,7 +120,7 @@ public structure that allow it to implement the API.
 GstMetaInfo will point to more information about the metadata and looks like this:
 
   struct _GstMetaInfo {
-    GQuark                     api;       /* api name */
+    GType                      api;       /* api type */
     GType                      type;      /* implementation type */
     gsize                      size;      /* size of the structure */
 
@@ -129,7 +129,7 @@ GstMetaInfo will point to more information about the metadata and looks like thi
     GstMetaTransformFunction   transform_func;
   };
 
-api will contain a GQuark of the metadata api. A repository of registered MetaInfo
+api will contain a GType of the metadata api. A repository of registered MetaInfo
 will be maintained by the core. We will register some common metadata structures
 in core and some media specific info for audio/video/text in -base. Plugins can
 register additional custom metadata.
@@ -369,11 +369,11 @@ We need to make sure that elements exchange metadata that they both understand,
 This is particulary important when the metadata describes the data layout in
 memory (such as strides).
 
-We would like to use the bufferpool negotiation system to negotiate the possible
-metadata that can be exchanged between elements.
+The ALLOCATION query is used to let upstream know what metadata we can suport.
 
-When deciding the allocation properties, we will also negotiate the buffer
-metadata structures that we can exchange.
+It is also possible to have a bufferpool add certain metadata to the buffers
+from the pool. This feature is activated by enabling a buffer option when
+configuring the pool.
 
 
 Notes