From ef406ae250aa650a52111a60369d9f0796714b00 Mon Sep 17 00:00:00 2001
From: Marko Gronroos <magi@vaadin.com>
Date: Fri, 18 Mar 2016 15:52:20 +0200
Subject: Fixed some missing images and broken xrefs, as well as problems in
 the getting-started chapter (#19639).

Change-Id: Ie8e371c059f70600bafcf781938ef35878f41324
---
 documentation/advanced/advanced-debug.asciidoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'documentation/advanced/advanced-debug.asciidoc')

diff --git a/documentation/advanced/advanced-debug.asciidoc b/documentation/advanced/advanced-debug.asciidoc
index 5415d0655e..3bbd6eb931 100644
--- a/documentation/advanced/advanced-debug.asciidoc
+++ b/documentation/advanced/advanced-debug.asciidoc
@@ -154,8 +154,8 @@ currently visible UI and makes a report of possible layout related problems. All
 detected layout problems are displayed in the log and also printed to the
 console.
 
-[[]]
-.Debug Window Showing the Result of Layout Analysis.
+[[figure.advanced.debug.hierarchy.analyze]]
+.Debug window showing the result of layout analysis.
 image::img/debug-window-analyze-layouts.png[]
 
 Clicking on a reported problem highlights the component with the problem in the
@@ -166,7 +166,7 @@ relative size inside a container (layout) that has undefined size in the
 particular direction (height or width). For example, adding a
 [classname]#Button# with 100% width inside a [classname]#VerticalLayout# with
 undefined width. In such a case, the error would look as shown in
-<<dummy/../../../framework//-overview.asciidoc#figure.advanced.debug.hierarchy.analyze,"">>.
+<<figure.advanced.debug.hierarchy.analyze>>.
 
 [classname]#CustomLayout# components can not be analyzed in the same way as
 other layouts. For custom layouts, the button analyzes all contained
-- 
cgit v1.2.3

