Remove broken links

Author: Noarkhh

basic_pipeline/12_Bin.md

@@ -78,4 +78,4 @@ defmodule Basic.Pipeline do
 end
 ```
 
-Combining the usage of the bin and [dynamic pads](03_DynamicPads.md) will result in an even cleaner and more scalable solution.
+Combining the usage of the bin and [dynamic pads](13_DynamicPads.md) will result in an even cleaner and more scalable solution.

basic_pipeline/13_DynamicPads.md

@@ -121,4 +121,4 @@ As you can see, we have created two `:input` pads: `:first` and `:second`. While
 
 As an exercise, you can try to modify the `lib/pipeline.ex` file and define a pipeline consisting of three parallel branches, being mixed in a single Mixer. Later on, you can check if the pipeline works as expected, by generating the input files out of the conversation in which participate three speakers.
 
-If you combine the approach taken in the chapter about [Bin](02_Bin.md) you can simplify this solution by reducing the size of the link defintions inside the pipeline.
+If you combine the approach taken in the chapter about [Bin](12_Bin.md) you can simplify this solution by reducing the size of the link defintions inside the pipeline.

broadcasting/05_RTMP_Pipeline.md

@@ -56,7 +56,7 @@ After providing the children's specifications, we are ready to connect the pads
  end
 ```
 
-The structure of links reflects the desired architecture of the application, described in the [chapter about system architecture](../videoroom/3_SystemArchitecture.md).
+The structure of links reflects the desired architecture of the application.
 `:src` has two output pads: the `:audio` pad and the `:video` pad, transferring the appropriate media tracks.
 The source's `:audio` pad is linked to the input `:audio` pad of the sink - along with the `:encoding` option. That option is an atom, describing the codec which is used to encode the media data - when it comes to audio data,
 we will be using AAC coded.

broadcasting/11_RTSP_Pipeline.md

@@ -1,4 +1,4 @@
-As explained in the [Architecture chapter](07_RTSP_Architecture.md), the pipeline will consist of a couple of elements, that will be processing the RTP stream.
+As explained in the [Architecture chapter](08_RTSP_Architecture.md), the pipeline will consist of a couple of elements, that will be processing the RTP stream.
 
 The flow of the pipeline will consist of three steps. First, when the pipeline is initialized we will start the Connection Manager, which will set up the RTP stream via the RTSP.
 Once that is finished, we will set up two initial elements in the pipeline - the `UDP Source` and `RTP SessionBin`, which will allow us to receive RTP packets and process them.

glossary/glossary.md

@@ -3,7 +3,7 @@
   - #### **Packet**
     It is a formatted unit of data transmitted over the network. To send data over the network it has to be fragmented into packets, which size is limited by [MTU(Maximum Transfer Unit)](https://en.wikipedia.org/wiki/Maximum_transmission_unit) - 1500 bytes when using [Ethernet](https://en.wikipedia.org/wiki/Ethernet_frame).  
   - #### **Frame**
-    'Frame' can refer to either [network frame](<https://en.wikipedia.org/wiki/Frame_(networking)>) or **media frame**, which is a basic data unit used by media coding formats. In particular, one media frame can represent a single image in a video.  
+    'Frame' can refer to either [network frame](https://en.wikipedia.org/wiki/Frame_(networking)) or **media frame**, which is a basic data unit used by media coding formats. In particular, one media frame can represent a single image in a video.  
   - #### **Track**
     A media track is equivalent to a single audio or video stream.  
   - #### **Simulcast**