Clarify Rust documentation for non-bazel users.

Fixes #298

PiperOrigin-RevId: 869199733

Author: protobuf-github-bot

content/reference/rust/rust-generated.md

@@ -29,37 +29,18 @@ Rust std types like `str`. See
 [Rust Proto Design Decisions](/reference/rust/rust-design-decisions)
 for more on this topic.
 
-## Generated Filenames {#filenames}
-
-Each `rust_proto_library` will be compiled as one crate. Most importantly, for
-every `.proto` file in the `srcs` of the corresponding `proto_library`, one Rust
-file is emitted, and all these files form a single crate.
-
-Files generated by the compiler vary between kernels. In general, the names of
-the output files are computed by taking the name of the `.proto` file and
-replacing the extension.
-
-Generated files:
-
-*   C++ kernel:
-    *   `.c.pb.rs` - generated Rust code
-    *   `.pb.thunks.cc` - generated C++ thunks (glue code that Rust code calls,
-        and that delegates to the C++ Protobuf APIs).
-*   C++ Lite kernel:
-    *   <same as C++ kernel>
-*   UPB kernel
-    *   `.u.pb.rs` - generated Rust code.
-
-Each `proto_library` will also have a `generated.rs` file which is treated as
-the entry point for the crate. That file will re-export the symbols from all the
-other Rust files in the crate.
-
 ## Packages {#packages}
 
 Unlike in most other languages, the `package` declarations in the `.proto` files
-are not used in Rust codegen. Instead, each `rust_proto_library(name =
-"some_rust_proto")` target emits a crate named `some_rust_proto` which contains
-the generated code for all `.proto` files in the target.
+are not used in Rust codegen.
+
+When `rust_proto_library` is used, the library will correspond to one crate. The
+name of the target is used as the crate name. Choose your library name
+correspondingly.
+
+When using Cargo, we recommend you `include!` the `generated.rs` entry point in
+a mod of an appropriate name, as in our
+[Example Crate](https://docs.rs/crate/protobuf-example).
 
 ## Messages {#messages}