From 3211b77affb739316fb41097a3110d8cf54e4c52 Mon Sep 17 00:00:00 2001
From: Kiriti Gowda <kiritigowda@gmail.com>
Date: Fri, 9 Feb 2024 10:41:03 -0800
Subject: [PATCH] decodingPipeline.md

Remove token
---
 docs/tutorial/decodingPipeline.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/tutorial/decodingPipeline.md b/docs/tutorial/decodingPipeline.md
index 0321891c49..b97cd1d2e4 100644
--- a/docs/tutorial/decodingPipeline.md
+++ b/docs/tutorial/decodingPipeline.md
@@ -1,6 +1,6 @@
 # Video decoding pipeline
 
-<p align="center"><img width="70%" src="https://raw.githubusercontent.com/ROCm/rocDecode/develop/docs/data/VideoDecoderPipeline.PNG?token=GHSAT0AAAAAACJXKIIZNT57RMQGFXUXZCVEZOGP37Q" /></p>
+<p align="center"><img width="70%" src="../data/VideoDecoderPipeline.PNG" /></p>
 
 There are three main components in the rocDecode shown in the figure above: Demuxer, Video Parser APIs, and Video Decode APIs.
 The Demuxer is based on FFMPEG. The demuxer extracts a segment of video data and sends it to the Video Parser. The parser then extracts crucial information such as picture and slice parameters, which is then sent to the Decoder APIs. These APIs submit the information to the hardware for the decoding of a frame. This process repeats in a loop until all frames have been decoded.