From 080c2a3997bb9c287b43e2e8a13fad8ce33b6129 Mon Sep 17 00:00:00 2001 From: Ravern Koh Date: Fri, 3 Nov 2023 15:40:17 +0800 Subject: [PATCH] remove remaining tocs --- docs/tutorials/RemovingFields.md | 4 ---- docs/tutorials/TracingCode.md | 3 --- 2 files changed, 7 deletions(-) diff --git a/docs/tutorials/RemovingFields.md b/docs/tutorials/RemovingFields.md index a99101477b2..161a9a56053 100644 --- a/docs/tutorials/RemovingFields.md +++ b/docs/tutorials/RemovingFields.md @@ -19,10 +19,6 @@ This tutorial aims to give you some practice on such a code 'removal' activity b However, if you have no such prior knowledge, removing a field can take a quite a bit of detective work. This tutorial takes you through that process. **At least have a read even if you don't actually do the steps yourself.** - -* Table of Contents -{:toc} - ## Safely deleting `Address` IntelliJ IDEA provides a refactoring tool that can identify *most* parts of a removal easily. Let’s try to use it as much as we can. diff --git a/docs/tutorials/TracingCode.md b/docs/tutorials/TracingCode.md index 9daa2829a49..eb906c38e66 100644 --- a/docs/tutorials/TracingCode.md +++ b/docs/tutorials/TracingCode.md @@ -10,9 +10,6 @@ title: "Tutorial: Tracing code" When trying to understand an unfamiliar code base, one common strategy used is to trace some representative execution path through the code base. One easy way to trace an execution path is to use a debugger to step through the code. In this tutorial, you will be using the IntelliJ IDEA’s debugger to trace the execution path of a specific user command. -* Table of Contents -{:toc} - ## Before we start Before we jump into the code, it is useful to get an idea of the overall structure and the high-level behavior of the application. This is provided in the 'Architecture' section of the developer guide. In particular, the architecture diagram (reproduced below), tells us that the App consists of several components.