From 7e082bcbbf39fe0877db05c8df2b524f8df18587 Mon Sep 17 00:00:00 2001
From: Mark Lu
Date: Tue, 19 Jul 2016 16:05:46 -0700
Subject: [PATCH] docs: fixed '@' signs that were escaped improperly
Bug: 29824906
Change-Id: Ibbf3e57e3f36cb0fa5cba0119ad30ca95850f2e9
---
docs/html/training/testing/ui-testing/espresso-testing.jd | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/html/training/testing/ui-testing/espresso-testing.jd b/docs/html/training/testing/ui-testing/espresso-testing.jd
index 7df67e7c23b84..d3d31debc3534 100644
--- a/docs/html/training/testing/ui-testing/espresso-testing.jd
+++ b/docs/html/training/testing/ui-testing/espresso-testing.jd
@@ -188,9 +188,9 @@ The following section describes how to create a new Espresso test in the JUnit 4
{@code ActivityTestRule} to reduce the amount of boilerplate code you need to write. By using
{@code ActivityTestRule}, the testing framework launches the activity under test
-before each test method annotated with {@code @Test} and before any method annotated with
-{@code @Before}. The framework handles shutting down the activity after the test finishes
-and all methods annotated with {@code @After} are run.
+before each test method annotated with @Test and before any method annotated with
+@Before. The framework handles shutting down the activity after the test finishes
+and all methods annotated with @After are run.
package com.example.android.testing.espresso.BasicSample;