[pitivi] docs: Remove unsupported images attributes markdown

[Thibault Saunier <tsaunier src gnome org>]

commit a5cb9ee4b128e728441975cc6ca906cb95db5080
Author: Alexandru Băluț <alexandru balut gmail com>
Date:   Wed Sep 12 00:02:03 2018 +0200

    docs: Remove unsupported images attributes markdown

 .../2008_design/2008_Architectural_Redesign/High-level_Design.md    | 5 ++---
 .../design/2008_design/2008_Architectural_Redesign/ObjectFactory.md | 2 +-
 docs/design/2008_design/2008_Architectural_Redesign/Pipeline.md     | 6 +++---
 docs/releases/0.91.md                                               | 2 +-
 4 files changed, 7 insertions(+), 8 deletions(-)
---
diff --git a/docs/design/2008_design/2008_Architectural_Redesign/High-level_Design.md 
b/docs/design/2008_design/2008_Architectural_Redesign/High-level_Design.md
index df06aeeb..1b02b3b2 100644
--- a/docs/design/2008_design/2008_Architectural_Redesign/High-level_Design.md
+++ b/docs/design/2008_design/2008_Architectural_Redesign/High-level_Design.md
@@ -15,8 +15,7 @@ PiTiVi is comprised of two main parts:
 
 # Core
 
-![Contents of
-Core](Top-level-core-only.png "Contents of Core"){width="300"}
+![Contents of Core](Top-level-core-only.png "Contents of Core")
 
 Core contains several essential components, of which the most important
 are:
@@ -54,7 +53,7 @@ If a User Interface is used, the Application object is its core
 counterpart.
 
 ![Project/Pipeline relationship and
-contents](Top-level-project-pipeline.png "Project/Pipeline relationship and contents"){width="300"}
+contents](Top-level-project-pipeline.png "Project/Pipeline relationship and contents")
 
 ### Project
 
diff --git a/docs/design/2008_design/2008_Architectural_Redesign/ObjectFactory.md 
b/docs/design/2008_design/2008_Architectural_Redesign/ObjectFactory.md
index ccb686a9..1956a6f6 100644
--- a/docs/design/2008_design/2008_Architectural_Redesign/ObjectFactory.md
+++ b/docs/design/2008_design/2008_Architectural_Redesign/ObjectFactory.md
@@ -148,4 +148,4 @@ of these use-case:
     a local, editable, copy.
 
 ![ObjectFactory
-hierarchy](Objectfactory-hierarchy.png "ObjectFactory hierarchy"){width="600"}
+hierarchy](Objectfactory-hierarchy.png "ObjectFactory hierarchy")
diff --git a/docs/design/2008_design/2008_Architectural_Redesign/Pipeline.md 
b/docs/design/2008_design/2008_Architectural_Redesign/Pipeline.md
index 994ba374..abdc4547 100644
--- a/docs/design/2008_design/2008_Architectural_Redesign/Pipeline.md
+++ b/docs/design/2008_design/2008_Architectural_Redesign/Pipeline.md
@@ -88,7 +88,7 @@ only have to work with 3 concepts:
 ## Viewing a File
 
 ![Example: Viewing a
-File](Pipeline-viewing-file.png "Example: Viewing a File"){width="200"}
+File](Pipeline-viewing-file.png "Example: Viewing a File")
 
 This is the simplest use-case for a Pipeline, which is viewing a File.
 
@@ -98,7 +98,7 @@ which connects a SourceProducer to a LocalSinksConsumer.
 ## Rendering a Timeline
 
 ![Example: Rendering a
-Timeline](Pipeline-rendering-timeline.png "Example: Rendering a Timeline"){width="200"}
+Timeline](Pipeline-rendering-timeline.png "Example: Rendering a Timeline")
 
 In this example, we are doing 2 actions at the same time:
 
@@ -139,4 +139,4 @@ When we are done rendering (because we got an EOS or such), we can then:
 # Relationship with GStreamer
 
 ![Relationship with
-GStreamer](Pipeline-gstreamer-relationship.png "Relationship with GStreamer"){width="200"}
+GStreamer](Pipeline-gstreamer-relationship.png "Relationship with GStreamer")
diff --git a/docs/releases/0.91.md b/docs/releases/0.91.md
index 0abd8287..52809265 100644
--- a/docs/releases/0.91.md
+++ b/docs/releases/0.91.md
@@ -63,7 +63,7 @@ details and historical context.
 
 ### Timeline and Playback
 
-![](images/Complex_layers_whiteboard_mockup_from_desktop_summit_2011.png 
"Complex_layers_whiteboard_mockup_from_desktop_summit_2011.png"){width="700"}
+![](images/Complex_layers_whiteboard_mockup_from_desktop_summit_2011.png 
"Complex_layers_whiteboard_mockup_from_desktop_summit_2011.png")
 
 -   Smooth, modern Clutter-based timeline with animations to enhance
     usability