Update refs for pwg -> plugin-development rename

https://bugzilla.gnome.org/show_bug.cgi?id=773976

markdown/application-development/advanced/autoplugging.md

@@ -63,7 +63,7 @@ we can look at methods GStreamer uses to setup pipelines for media
 handling and for media type detection.
 
 [pad-caps]: application-development/basics/pads.md#capabilities-of-a-pad
-[pwg-type-defs]: pwg/advanced/building-types.md
+[pwg-type-defs]: plugin-development/advanced/building-types.md
 
 ## Media stream type detection
 

markdown/application-development/appendix/compiling.md

@@ -9,8 +9,7 @@ and shipping your applications and plugins.
 
 ## Embedding static elements in your application
 
-The [Plugin Writer's
+The [Plugin Writer's Guide](plugin-development/index.md)
-Guide](http://gstreamer.freedesktop.org/data/doc/gstreamer/head/pwg/html/index.html)
 describes in great detail how to write elements for the GStreamer
 framework. In this section, we will solely discuss how to embed such
 elements statically in your application. This can be useful for

markdown/application-development/basics/bins.md

@@ -117,8 +117,7 @@ powerful and versatile custom bin like this: the playbin element.)
 
 Custom bins can be created with a plugin or from the application. You
 will find more information about creating custom bin in the [Plugin
-Writers
+Writer's Guide](plugin-development/index.md)
-Guide](http://gstreamer.freedesktop.org/data/doc/gstreamer/head/pwg/html/index.html).
 
 Examples of such custom bins are the playbin and uridecodebin elements
 from[gst-plugins-base](http://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-plugins/html/index.html).

markdown/application-development/basics/pads.md

@@ -146,8 +146,7 @@ that can flow or currently flows through the pad by using capabilities.
 Here, we will briefly describe what capabilities are and how to use
 them, enough to get an understanding of the concept. For an in-depth
 look into capabilities and a list of all capabilities defined in
-GStreamer, see the [Plugin Writers
+GStreamer, see the [Plugin Writers Guide](plugin-development/index.md)
-Guide](http://gstreamer.freedesktop.org/data/doc/gstreamer/head/pwg/html/index.html).
 
 Capabilities are attached to pad templates and to pads. For pad
 templates, it will describe the types of media that may stream over a

markdown/application-development/index.md

@@ -27,7 +27,7 @@ but also at other forms of media processing (capture, editing, etc.).
 This book is about GStreamer from an application developer's point of
 view; it describes how to write a GStreamer application using the
 GStreamer libraries and tools. For an explanation about writing plugins,
-we suggest the [Plugin Writers Guide](pwg/index.md).
+we suggest the [Plugin Writer's Guide](plugin-development/index.md).
 
 Also check out the other documentation available on the [GStreamer web
 site](http://gstreamer.freedesktop.org/documentation/).

markdown/plugin-development/advanced/events.md

@@ -172,9 +172,11 @@ WRITEME
 ### Caps
 
 The CAPS event contains the format description of the following buffers.
-See [Caps negotiation](pwg/advanced/negotiation.md) for more information
+See [Caps negotiation][caps-negotiation] for more information
 about negotiation.
 
+[caps-negotiation]: plugin-development/advanced/negotiation.md
+
 ### Segment
 
 A segment event is sent downstream to announce the range of valid
@@ -214,9 +216,8 @@ clipping, for example).
 Tagging events are being sent downstream to indicate the tags as parsed
 from the stream data. This is currently used to preserve tags during
 stream transcoding from one format to the other. Tags are discussed
-extensively in [Tagging (Metadata and
+extensively in [Tagging (Metadata and Streaminfo)][metadata]. Most elements
-Streaminfo)](pwg/advanced/tagging.md). Most elements will simply
+will simply forward the event by calling `gst_pad_event_default ()`.
-forward the event by calling `gst_pad_event_default ()`.
 
 The tag event is created using the function `gst_event_new_tag ()`, but
 more often elements will send a tag event downstream that will be
@@ -224,8 +225,10 @@ converted into a message on the bus by sink elements. All of these
 functions require a filled-in taglist as argument, which they will take
 ownership of.
 
-Elements parsing this event can use the function `gst_event_parse_tag
+Elements parsing this event can use the function `gst_event_parse_tag ()` to
-()` to acquire the taglist that the event contains.
+acquire the taglist that the event contains.
+
+[metadata]: plugin-development/advanced/tagging.md
 
 ### End of Stream (EOS)
 
@@ -306,8 +309,9 @@ running\_time is set back to 0.
 ### Quality Of Service (QOS)
 
 The QOS event contains a report about the current real-time performance
-of the stream. See more info in [Quality Of Service
+of the stream. See more info in [Quality Of Service (QoS)][qos].
-(QoS)](pwg/advanced/qos.md).
+
+[qos]: plugin-development/advanced/qos.md
 
 ### Seek Request
 

markdown/plugin-development/advanced/interfaces.md

@@ -4,11 +4,10 @@ title: Interfaces
 
 # Interfaces
 
-Previously, in the chapter [Adding
+Previously, in the chapter [Adding Properties][plugin-properties], we have
-Properties](pwg/building/args.md), we have introduced the concept of
+introduced the concept of GObject properties of controlling an element's
-GObject properties of controlling an element's behaviour. This is very
+behaviour. This is very powerful, but it has two big disadvantages: first of
-powerful, but it has two big disadvantages: first of all, it is too
+all, it is too generic, and second, it isn't dynamic.
-generic, and second, it isn't dynamic.
 
 The first disadvantage is related to the customizability of the end-user
 interface that will be built to control the element. Some properties are
@@ -40,7 +39,9 @@ One important note: interfaces do *not* replace properties. Rather,
 interfaces should be built *next to* properties. There are two important
 reasons for this. First of all, properties can be more easily
 introspected. Second, properties can be specified on the commandline
-(`gst-launch`).
+(`gst-launch-1.0`).
+
+[plugin-properties]: plugin-development/building/args.md
 
 ## How to Implement Interfaces
 
@@ -124,7 +125,7 @@ WRITEME
 
 ## Video Overlay Interface
 
-The \#GstVideoOverlay interface is used for 2 main purposes :
+The `GstVideoOverlay` interface is used for 2 main purposes :
 
   - To get a grab on the Window where the video sink element is going to
     render. This is achieved by either being informed about the Window
@@ -133,8 +134,8 @@ The \#GstVideoOverlay interface is used for 2 main purposes :
     rendering.
 
   - To force a redrawing of the latest video frame the video sink
-    element displayed on the Window. Indeed if the \#GstPipeline is in
+    element displayed on the Window. Indeed if the `GstPipeline` is in
-    \#GST\_STATE\_PAUSED state, moving the Window around will damage its
+    `GST\_STATE\_PAUSED` state, moving the Window around will damage its
     content. Application developers will want to handle the Expose
     events themselves and force the video sink element to refresh the
     Window's content.

markdown/plugin-development/appendix/porting.md

@@ -26,7 +26,7 @@ also need a rewrite, which will take about the same amount of time.
 
   - In 0.10, buffers have caps attached to them. Elements should
     allocate new buffers with `gst_pad_alloc_buffer ()`. See [Caps
-    negotiation](pwg/advanced/negotiation.md) for more details.
+    negotiation](plugin-development/advanced/negotiation.md) for more details.
 
   - Most functions returning an object or an object property have been
     changed to return its own reference rather than a constant reference
@@ -46,21 +46,21 @@ also need a rewrite, which will take about the same amount of time.
     some more work. Pads get assigned a scheduling mode, based on which
     they can either operate in random access-mode, in pipeline driving
     mode or in push-mode. all this is documented in detail in [Different
-    scheduling modes](pwg/advanced/scheduling.md). As a result of this, the
+    scheduling modes](plugin-development/advanced/scheduling.md). As a result of this, the
     bytestream object no longer exists. Elements requiring byte-level
     access should now use random access on their sinkpads.
 
   - Negotiation is asynchronous. This means that downstream negotiation
     is done as data comes in and upstream negotiation is done whenever
     renegotiation is required. All details are described in [Caps
-    negotiation](pwg/advanced/negotiation.md).
+    negotiation](plugin-development/advanced/negotiation.md).
 
   - For as far as possible, elements should try to use existing base
     classes in 0.10. Sink and source elements, for example, could derive
     from `GstBaseSrc` and `GstBaseSink`. Audio sinks or sources could
     even derive from audio-specific base classes. All existing base
     classes have been discussed in [Pre-made base
-    classes](pwg/other/base.md) and the next few chapters.
+    classes](plugin-development/other/base.md) and the next few chapters.
 
   - In 0.10, event handling and buffers are separated once again. This
     means that in order to receive events, one no longer has to set the
@@ -88,7 +88,7 @@ also need a rewrite, which will take about the same amount of time.
     need to be able to accept and process data already in the
     `GST_STATE_PAUSED` state now (i.e. when prerolling the pipeline).
     More details can be found in [What are
-    states?](pwg/building/statemanage-states.md).
+    states?](plugin-development/building/statemanage-states.md).
 
   - If your plugin's state change function hasn't been superseded by
     virtual start() and stop() methods of one of the new base classes,

markdown/plugin-development/building/boiler.md

@@ -259,8 +259,8 @@ details on this.
 Pads are created from these static templates in the element's `_init ()`
 function using `gst_pad_new_from_static_template ()`. In order to create
 a new pad from this template using `gst_pad_new_from_static_template
-()`, you will need to declare the pad template as a global variable.
+()`, you will need to declare the pad template as a global variable. More on
-More on this subject in [Specifying the pads](pwg/building/pads.md).
+this subject in [Specifying the pads][pads].
 
     static GstStaticPadTemplate sink_factory = [..],
         src_factory = [..];
@@ -309,8 +309,9 @@ Values surrounded by curly brackets (“{” and “}”) are lists, values
 surrounded by square brackets (“\[” and “\]”) are ranges. Multiple sets
 of types are supported too, and should be separated by a semicolon
 (“;”). Later, in the chapter on pads, we will see how to use types
-to know the exact format of a stream: [Specifying the
+to know the exact format of a stream: [Specifying the pads][pads].
-pads](pwg/building/pads.md).
+
+[pads]: plugin-development/building/pads.md
 
 ## Constructor Functions
 

markdown/plugin-development/building/index.md

@@ -17,6 +17,7 @@ single output pad. The filter will, at first, simply pass media and
 event data from its sink pad to its source pad without modification. But
 by the end of this part of the guide, you will learn to add some more
 interesting functionality, including properties and signal handlers. And
-after reading the next part of the guide, [Advanced Filter
+after reading the next part of the guide, [Advanced Filter Concepts][advanced],
-Concepts](pwg/advanced/index.md), you will be able to add even more
+you will be able to add even more functionality to your plugins.
-functionality to your plugins.
+
+[advanced]: plugin-development/advanced/index.md

markdown/plugin-development/building/statemanage-states.md

@@ -52,7 +52,7 @@ card or render video pictures to an image sink.
 ## Managing filter state
 
 If at all possible, your element should derive from one of the new base
-classes ([Pre-made base classes](pwg/other/base.md)). There are
+classes ([Pre-made base classes](plugin-development/other/base.md)). There are
 ready-made general purpose base classes for different types of sources,
 sinks and filter/transformation elements. In addition to those,
 specialised base classes exist for audio and video elements and others.

markdown/plugin-development/introduction/basics.md

@@ -126,8 +126,8 @@ Events may contain several of the following items:
   - The other contents of the event depend on the specific event type.
 
 Events will be discussed extensively in [Events: Seeking, Navigation and
-More](pwg/advanced/events.md). Until then, the only event that will
+More](plugin-development/advanced/events.md). Until then, the only event that
-be used is the *EOS* event, which is used to indicate the end-of-stream
+will be used is the *EOS* event, which is used to indicate the end-of-stream
 (usually end-of-file).
 
 See the *GStreamer Library Reference* for the current implementation
@@ -157,7 +157,7 @@ from a downstream peer through a GstBufferPool or GstAllocator. Elements
 can ask a GstBufferPool or GstAllocator from the downstream peer
 element. If downstream is able to provide these objects, upstream can
 use them to allocate buffers. See more in [Memory
-allocation](pwg/advanced/allocation.md).
+allocation](plugin-development/advanced/allocation.md).
 
 Many sink elements have accelerated methods for copying data to
 hardware, or have direct access to hardware. It is common for these
@@ -183,7 +183,7 @@ for ensuring that the parameters required to fully specify a format
 match up correctly when linking pads between elements. Each link that is
 made between elements has a specified type and optionally a set of
 properties. See more about caps negotiation in [Caps
-negotiation](pwg/advanced/negotiation.md).
+negotiation](plugin-development/advanced/negotiation.md).
 
 ### The Basic Types
 
@@ -192,7 +192,7 @@ of a few of the basic types used for buffers in GStreamer. The table
 contains the name ("media type") and a description of the type, the
 properties associated with the type, and the meaning of each property. A
 full list of supported types is included in [List of Defined
-Types](pwg/advanced/building-types.md#list-of-defined-types).
+Types](plugin-development/advanced/building-types.md#list-of-defined-types).
 
 <table>
 <caption>Table of Example Types</caption>

markdown/plugin-development/introduction/preface.md

@@ -89,7 +89,7 @@ large parts. Each part addresses a particular broad topic concerning
 GStreamer plugin development. The parts of this guide are laid out in
 the following order:
 
-  - [Building a Plugin](pwg/building/index.md) - Introduction to the
+  - [Building a Plugin][building] - Introduction to the
     structure of a plugin, using an example audio filter for
     illustration.
 
@@ -98,24 +98,22 @@ the following order:
     and setting up the basics so it can receive data from and send data
     to neighbour elements. The discussion begins by giving examples of
     generating the basic structures and registering an element in
-    [Constructing the Boilerplate](pwg/building/boiler.md). Then,
+    [Constructing the Boilerplate][boilerplate]. Then,
     you will learn how to write the code to get a basic filter plugin
-    working in [Specifying the pads](pwg/building/pads.md), [The
+    working in [Specifying the pads][pads], [The chain function][chainfunc]
-    chain function](pwg/building/chainfn.md) and [What are
+    and [What are states?][states].
-    states?](pwg/building/statemanage-states.md).
 
     After that, we will show some of the GObject concepts on how to make
     an element configurable for applications and how to do
     application-element interaction in [Adding
-    Properties](pwg/building/args.md) and
+    Properties][properties] and [Signals][signals]. Next, you will learn to
-    [Signals](pwg/building/signals.md). Next, you will learn to
     build a quick test application to test all that you've just learned
-    in [Building a Test Application](pwg/building/testapp.md). We
+    in [Building a Test Application][testapp]. We
     will just touch upon basics here. For full-blown application
     development, you should look at [the Application Development
     Manual](application-development/index.md).
 
-  - [Advanced Filter Concepts](pwg/advanced/index.md) - Information on
+  - [Advanced Filter Concepts][advanced] - Information on
     advanced features of GStreamer plugin development.
 
     After learning about the basic steps, you should be able to create a
@@ -127,19 +125,18 @@ the following order:
     order, most of them don't require knowledge from other sections.
 
     The first chapter, named [Different scheduling
-    modes](pwg/advanced/scheduling.md), will explain some of the basics of
+    modes][scheduling], will explain some of the basics of
     element scheduling. It is not very in-depth, but is mostly some sort
     of an introduction on why other things work as they do. Read this
     chapter if you're interested in GStreamer internals. Next, we will
     apply this knowledge and discuss another type of data transmission
-    than what you learned in [The chain
+    than what you learned in [The chain function][chainfunc]: [Different
-    function](pwg/building/chainfn.md): [Different scheduling
+    scheduling modes][scheduling]. Loop-based elements will give you
-    modes](pwg/advanced/scheduling.md). Loop-based elements will give you
     more control over input rate. This is useful when writing, for
     example, muxers or demuxers.
 
     Next, we will discuss media identification in GStreamer in [Types
-    and Properties](pwg/advanced/building-types.md). You will learn how to
+    and Properties][types]. You will learn how to
     define new media types and get to know a list of standard media
     types defined in GStreamer.
 
@@ -147,37 +144,34 @@ the following order:
     sometimes-pads, which are pads that are created dynamically, either
     because the application asked for it (request) or because the media
     stream requires it (sometimes). This will be in [Request and
-    Sometimes pads](pwg/advanced/request.md).
+    Sometimes pads][request-pads].
 
-    The next chapter, [Clocking](pwg/advanced/clock.md), will
+    The next chapter, [Clocking][clocks], will
     explain the concept of clocks in GStreamer. You need this
     information when you want to know how elements should achieve
     audio/video synchronization.
 
     The next few chapters will discuss advanced ways of doing
     application-element interaction. Previously, we learned on the
-    GObject-ways of doing this in [Adding
+    GObject-ways of doing this in [Adding Properties][properties] and
-    Properties](pwg/building/args.md) and
+    [Signals][signals]. We will discuss dynamic
-    [Signals](pwg/building/signals.md). We will discuss dynamic
     parameters, which are a way of defining element behaviour over time
-    in advance, in [Supporting Dynamic Parameters](pwg/advanced/dparams.md).
+    in advance, in [Supporting Dynamic Parameters][dynamic-params].
-    Next, you will learn about interfaces in
+    Next, you will learn about interfaces in [Interfaces][interfaces].
-    [Interfaces](pwg/advanced/interfaces.md). Interfaces are very
+    Interfaces are very target- specific ways of application-element
-    target- specific ways of application-element interaction, based on
+    interaction, based on GObject's GInterface. Lastly, you will learn about
-    GObject's GInterface. Lastly, you will learn about how metadata is
+    how metadata is handled in GStreamer in [Tagging (Metadata and
-    handled in GStreamer in [Tagging (Metadata and
+    Streaminfo)][tagging].
-    Streaminfo)](pwg/advanced/tagging.md).
 
-    The last chapter, [Events: Seeking, Navigation and
+    The last chapter, [Events: Seeking, Navigation and More][events], will
-    More](pwg/advanced/events.md), will discuss the concept of
+    discuss the concept of events in GStreamer. Events are another way of
-    events in GStreamer. Events are, on the one hand, another way of
+    doing application-element interaction. They take care of seeking, for
-    doing application-element interaction. It takes care of seeking, for
+    example. They are also yet another a way in which elements
-    example. On the other hand, it is also a way in which elements
     interact with each other, such as letting each other know about
     media stream discontinuities, forwarding tags inside a pipeline and
     so on.
 
-  - [Creating special element types](pwg/other/index.md) - Explanation of
+  - [Creating special element types][element-types] - Explanation of
     writing other plugin types.
 
     Because the first two parts of the guide use an audio filter as an
@@ -186,15 +180,12 @@ the following order:
     sources, sinks, and autopluggers. This part of the guide presents
     the issues that arise when working on these more specialized plugin
     types. The chapter starts with a special focus on elements that can
-    be written using a base-class ([Pre-made base
+    be written using a base-class ([Pre-made base classes][base-classes]),
-    classes](pwg/other/base.md)), and later also goes into writing
+    and later also goes into writing special types of elements in [Writing a
-    special types of elements in [Writing a Demuxer or
+    Demuxer or Parser][one-to-n], [Writing a N-to-1 Element or Muxer][n-to-one]
-    Parser](pwg/other/oneton.md), [Writing a N-to-1 Element or
+    and [Writing a Manager][manager].
-    Muxer](pwg/other/ntoone.md) and [Writing a
-    Manager](pwg/other/manager.md).
 
-  - [Appendices](pwg/appendix/index.md) - Further information for plugin
+  - [Appendices][appendix] - Further information for plugin developers.
-    developers.
 
     The appendices contain some information that stubbornly refuses to
     fit cleanly in other sections of the guide. Most of this section is
@@ -202,15 +193,11 @@ the following order:
 
 The remainder of this introductory part of the guide presents a short
 overview of the basic concepts involved in GStreamer plugin development.
-Topics covered include [Elements and
+Topics covered include [Elements and Plugins][intro-elements],
-Plugins](pwg/introduction/basics.md#elements-and-plugins),
+[Pads][intro-pads], [GstMiniObject, Buffers and Events][intro-miniobjects]
-[Pads](pwg/introduction/basics.md#pads), [GstMiniObject, Buffers and
+and [Media types and Properties][intro-mediatypes]. If you are already
-Events](pwg/introduction/basics.md#gstminiobject-buffers-and-events) and
+familiar with this information, you can use this short overview to
-[Media types and
+refresh your memory, or you can skip to [Building a Plugin][building].
-Properties](pwg/introduction/basics.md#media-types-and-properties). If you
-are already familiar with this information, you can use this short
-overview to refresh your memory, or you can skip to [Building a
-Plugin](pwg/building/index.md).
 
 As you can see, there a lot to learn, so let's get started\!
 
@@ -221,3 +208,31 @@ As you can see, there a lot to learn, so let's get started\!
   - Adding new media types to the registry along with typedetect
     functions. This will allow your plugin to operate on a completely
     new media type.
+
+[building]: plugin-development/building/index.md
+[boilerplate]: plugin-development/building/boiler.md
+[pads]: plugin-development/building/pads.md
+[chainfunc]: plugin-development/building/chainfn.md
+[states]: plugin-development/building/statemanage-states.md
+[properties]: plugin-development/building/args.md
+[signals]: plugin-development/building/signals.md
+[testapp]: plugin-development/building/testapp.md
+[advanced]: plugin-development/advanced/index.md
+[scheduling]: plugin-development/advanced/scheduling.md
+[types]: plugin-development/advanced/building-types.md
+[request-pads]: plugin-development/advanced/request.md
+[clocks]: plugin-development/advanced/clock.md
+[dynamic-params]: plugin-development/advanced/dparams.md
+[interfaces]: plugin-development/advanced/interfaces.md
+[tagging]: plugin-development/advanced/tagging.md
+[events]: plugin-development/advanced/events.md
+[element-types]: plugin-development/other/index.md
+[base-classes]: plugin-development/other/base.md
+[one-to-n]: plugin-development/other/oneton.md
+[n-to-one]: plugin-development/other/ntoone.md
+[manager]: plugin-development/other/manager.md
+[appendix]: plugin-development/appendix/index.md
+[intro-elements]: plugin-development/introduction/basics.md#elements-and-plugins
+[intro-pads]: plugin-development/introduction/basics.md#pads
+[intro-miniobjects]: plugin-development/introduction/basics.md#gstminiobject-buffers-and-events
+[intro-mediatypes]: plugin-development/introduction/basics.md#media-types-and-properties

markdown/plugin-development/other/base.md

@@ -136,11 +136,10 @@ videosink:
 
 ## Writing a source
 
-In the previous part, particularly [Providing random
+In the previous part, particularly [Providing random access][random-access],
-access](pwg/advanced/scheduling.md#providing-random-access), we have learned
+we have learned that some types of elements can provide random access. This
-that some types of elements can provide random access. This applies most
+applies most definitely to source elements reading from a randomly seekable
-definitely to source elements reading from a randomly seekable location,
+location, such as file sources. However, other source elements may be better
-such as file sources. However, other source elements may be better
 described as a live source element, such as a camera source, an audio
 card source and such; those are not seekable and do not provide
 byte-exact access. For all such use cases, GStreamer provides two base
@@ -169,6 +168,8 @@ It is possible to use special memory, such as X server memory pointers
 or `mmap ()`'ed memory areas, as data pointers in buffers returned from
 the `create()` virtual function.
 
+[random-access]: plugin-development/advanced/scheduling.md#providing-random-access
+
 ### Writing an audio source
 
 An audio source is nothing more but a special case of a pushsource.

markdown/plugin-development/other/ntoone.md

@@ -5,8 +5,8 @@ title: Writing a N-to-1 Element or Muxer
 # Writing a N-to-1 Element or Muxer
 
 N-to-1 elements have been previously mentioned and discussed in both
-[Request and Sometimes pads](pwg/advanced/request.md) and in
+[Request and Sometimes pads][request-pads] and in
-[Different scheduling modes](pwg/advanced/scheduling.md). The main noteworthy
+[Different scheduling modes][scheduling]. The main noteworthy
 thing about N-to-1 elements is that each pad is push-based in its own
 thread, and the N-to-1 element synchronizes those streams by
 expected-timestamp-based logic. This means it lets all streams wait
@@ -21,3 +21,6 @@ buffer from each input and giving you the one with earliest timestamp.
 If you need anything more difficult, such as "don't-grab-a-new-buffer
 until a given timestamp" or something like that, you'll need to do this
 yourself.
+
+[request-pads]: plugin-development/advanced/request.md
+[scheduling]: plugin-development/advanced/scheduling.md

markdown/plugin-development/other/oneton.md

@@ -12,10 +12,10 @@ will be offered. Parsers are demuxers with only one source pad. Also,
 they only cut the stream into buffers, they don't touch the data
 otherwise.
 
-As mentioned previously in [Caps negotiation](pwg/advanced/negotiation.md),
+As mentioned previously in [Caps negotiation][negotiation],
 demuxers should use fixed caps, since their data type will not change.
 
-As discussed in [Different scheduling modes](pwg/advanced/scheduling.md),
+As discussed in [Different scheduling modes][scheduling],
 demuxer elements can be written in multiple ways:
 
   - They can be the driving force of the pipeline, by running their own
@@ -31,5 +31,8 @@ written in random access mode. Although simple playback will mostly work
 if your element only accepts one mode, it may be required to implement
 multiple modes to work in combination with all sorts of applications,
 such as editing. Also, performance may become better if you implement
-multiple modes. See [Different scheduling modes](pwg/advanced/scheduling.md)
+multiple modes. See [Different scheduling modes][scheduling]
 to see how an element can accept multiple scheduling modes.
+
+[negotiation]: plugin-development/advanced/negotiation.md
+[scheduling]: plugin-development/advanced/scheduling.md