docs: Rename 'Call back into Wolfram from Rust' to 'Evaluate Wolfram code from Rust' (#39)

I changed my mind. The phrase 'call back' is a bit more technical and less
likely to be familiar than simply 'evaluate', which is a clearer statement of
what's happening.

Additionally, a 'callback function' (i.e. a function pointer / closure)
is one mechanism for executing code across a library / language boundary, but that
is not at all the mechanism used for Rust -> Wolfram evaluations. The new name
avoids this potentially misleading connotation.

Author: ConnorGray

wolfram-library-link/RustLink/Examples/Docs/CallBackIntoWolframFromRust/GenerateMessage.wlt renamed to wolfram-library-link/RustLink/Examples/Docs/EvaluateWolframCodeFromRust/GenerateMessage.wlt

@@ -3,6 +3,6 @@ mod convert {
     mod using_expr;
 }
 
-mod call_back_into_wolfram_from_rust {
+mod evaluate_wolfram_code_from_rust {
     mod generate_message;
 }

wolfram-library-link/examples/docs/call_back_into_wolfram_from_rust/generate_message.rs renamed to wolfram-library-link/examples/docs/evaluate_wolfram_code_from_rust/generate_message.rs

@@ -3,9 +3,9 @@
 //! ### How Tos
 //!
 //! * [How To: Convert Between Rust and Wolfram Types][converting_between_rust_and_wolfram_types]
-//! * [How To: Call back into Wolfram from Rust][call_back_into_wolfram_from_rust]
+//! * [How To: Evaluate Wolfram code from Rust][evaluate_wolfram_code_from_rust]
 
 #![allow(unused_imports)]
 
-pub mod call_back_into_wolfram_from_rust;
 pub mod converting_between_rust_and_wolfram_types;
+pub mod evaluate_wolfram_code_from_rust;

wolfram-library-link/examples/docs/main.rs

@@ -1,21 +1,23 @@
 /*!
-# How To: Call back into Wolfram from Rust
+# How To: Evaluate Wolfram code from Rust
 
 
 ## Generating Wolfram messages from Rust
 
-Suppose you want to generate a Wolfram [Message\[..\]][ref/Message] from within Rust.
+Suppose you want to generate a Wolfram [`Message[..]`][ref/Message] from within Rust.
 
 The easiest way to accomplish this is to construct an appropriate Wolfram expression
 using the [`Expr`] type, and then use the [`evaluate()`] function to call back into
 Wolfram to evaluate that expression.
 
+[ref/Message]: https://reference.wolfram.com/language/ref/Message.html
+
 **Rust**
 
 ```rust
 # mod scope {
 */
-#![doc = include_str!("../../examples/docs/call_back_into_wolfram_from_rust/generate_message.rs")]
+#![doc = include_str!("../../examples/docs/evaluate_wolfram_code_from_rust/generate_message.rs")]
 /*!
 # }
 ```
@@ -24,7 +26,7 @@ Wolfram to evaluate that expression.
 
 ```wolfram
 */
-#![doc = include_str!("../../RustLink/Examples/Docs/CallBackIntoWolframFromRust/GenerateMessage.wlt")]
+#![doc = include_str!("../../RustLink/Examples/Docs/EvaluateWolframCodeFromRust/GenerateMessage.wlt")]
 /*!
 ```
 

wolfram-library-link/src/docs.rs

@@ -126,7 +126,7 @@
 //! # Documentation
 //!
 //! * [How To: Convert Between Rust and Wolfram Types][crate::docs::converting_between_rust_and_wolfram_types]
-//! * [How To: Call back into Wolfram from Rust][docs::call_back_into_wolfram_from_rust]
+//! * [How To: Evaluate Wolfram code from Rust][docs::evaluate_wolfram_code_from_rust]
 //!
 //! *See the [`docs`] module for a complete list of available long-form documentation.*
 //!