update readme

README.md

@@ -108,7 +108,7 @@ A simple example:
 ```proto
 syntax = "proto3";
 
-package com.toasttab.protokt.sample;
+package toasttab.protokt.sample;
 
 message Sample {
   string sample_field = 1;
@@ -120,7 +120,7 @@ will produce:
 ```kotlin
 /*
  * Generated by protokt version <version>. Do not modify.
- * Source: com/toasttab/protokt/sample/sample.proto
+ * Source: toasttab/protokt/sample/sample.proto
  */
 
 package com.toasttab.protokt.sample
@@ -134,7 +134,7 @@ import com.toasttab.protokt.rt.Tag
 import com.toasttab.protokt.rt.UnknownFieldSet
 import com.toasttab.protokt.rt.sizeof
 
-@KtGeneratedMessage("com.toasttab.protokt.sample.Sample")
+@KtGeneratedMessage("toasttab.protokt.sample.Sample")
 class Sample
 private constructor(
     val sampleField: String,
@@ -275,7 +275,7 @@ syntax = "proto3";
 
 import "protokt/protokt.proto";
 
-package com.example;
+package example;
 
 option (protokt.file).kotlin_package = "com.package";
 
@@ -295,6 +295,8 @@ InputStream, or others.
 
 #### Enums
 
+##### Representation
+
 Protokt represents enum fields as sealed classes with an integer value and name.
 Protobuf enums cannot be represented as Kotlin enum classes since Kotlin enum
 classes are closed and cannot represent unknown values. The Protocol Buffers
@@ -327,6 +329,13 @@ sealed class PhoneType(
 }
 ```
 
+##### Naming
+
+To keep enums ergonomic while promoting protobuf best-practices, enums that have
+all values
+[prefixed with the enum type name](https://developers.google.com/protocol-buffers/docs/style#enums)
+will have that prefix stripped in their Kotlin representations.
+
 #### Other Notes
 
 - `optimize_for` is ignored.
@@ -336,6 +345,7 @@ sealed class PhoneType(
 single property.
 - `bytes` fields are wrapped in the protokt `Bytes` class to ensure immutability
 akin to `protobuf-java`'s `ByteString`.
+- Protokt implements proto3's `optional`.
 
 ### Extensions