diff --git a/specification/compatibility/opencensus.md b/specification/compatibility/opencensus.md
index fff046980a9..e0b1a7cd098 100644
--- a/specification/compatibility/opencensus.md
+++ b/specification/compatibility/opencensus.md
@@ -137,18 +137,14 @@ Finally, the Application would update all usages of OpenCensus to OpenTelemetry.
 
 ### Requirements
 
-OpenTelemetry<->OpenCensus compatibility has the following requirements:
+The OpenTelemetry<->OpenCensus trace bridge has the following requirements:
 
-1. OpenCensus has no hard dependency on OpenTelemetry
-2. Minimal changes to OpenCensus for implementation
-3. Easy for users to use, ideally no change to their code
-
-Additionally, for tracing there are the following requirements:
-
-1. Maintain parent-child span relationship between applications and libraries
-2. Maintain span link relationships between applications and libraries
-
-This component MUST be an optional dependency.
+* OpenCensus has no hard dependency on OpenTelemetry
+* Minimal changes to OpenCensus for implementation
+* Easy for users to use, ideally no change to their code
+* Maintain parent-child span relationship between applications and libraries
+* Maintain span link relationships between applications and libraries
+* This component MUST be an optional dependency.
 
 ### Creating Spans in OpenCensus
 
@@ -176,7 +172,7 @@ Note: resources appear not to be usable in the "API" section of OpenCensus.
 
 Below are listed known incompatibilities between OpenTelemetry and OpenCensus
 specifications.   Applications leveraging unspecified behavior from OpenCensus
-that *is* specified incompatibly within OpenTelemetry are not eligble for
+that _is_ specified incompatibly within OpenTelemetry are not eligble for
 using the OpenCensus <-> OpenTelemetry bridge.
 
 1. In OpenCensus, there is [no specification](https://github.com/census-instrumentation/opencensus-specs/blob/master/trace/Span.md#span-creation)