Fix README.md with correct method names

Author: szuend

README.md

@@ -35,24 +35,30 @@ import { decode } from "@chrome-devtools/source-map-scopes-codec";
 const scopeInformation = decode(sourceMap);
 ```
 
+### Scope Builder
+
 The library also contains a builder that makes creating structured scope information easier:
 
 ```js
 import { ScopeInfoBuilder } from "@chrome-devtools/source-map-scopes-codec";
 
 const scopeInformation = new ScopeInfoBuilder()
-    .addScope(0, 0, { kind: "Global" })
-        .addScope(5, 10)
-        .setScopeKind("Function")      // Same as passing 'kind' to 'addScope'.
-        .setScopeName("foo")           // Same as passing 'name' to 'addScope'.
+    .startScope(0, 0, { kind: "Global" })
+        .startScope(5, 10)
+        .setScopeKind("Function")      // Same as passing 'kind' to 'startScope'.
+        .setScopeName("foo")           // Same as passing 'name' to 'startScope'.
         .endScope(10, 5)
     .endScope(11, 1)
-    .addRange(0, 0, { scope: 0 })
-        .addRange(0, 10)
-        .setRangeScopeDefinition(1)    // Same as passing 'scope' to 'addRange'.
+    .startRange(0, 0, { scope: 0 })
+        .startRange(0, 10)
+        .setRangeScopeDefinition(1)    // Same as passing 'scope' to 'startRange'.
         .endRange(0, 15)
     .endRange(1, 1)
     .build();
 ```
 
 There is also a `SafeScopeInfoBuilder` that checks that scopes and ranges are well nested and some other integrity constraints (e.g. definition scopes are known).
+
+## Missing features
+
+The library is currently missing support for encoding/decoding sub-range bindings. It will be added in the next release.