Only run Rust workflow on particular set of files (#387)

Author: citizen-stig

.github/workflows/rust.yml

@@ -2,9 +2,13 @@ name: Rust
 
 on:
   push:
-    branches: ["main"]
+    branches: [ "main" ]
+    paths-ignore:
+      - '**.md'
   pull_request:
-    branches: ["main"]
+    branches: [ "main" ]
+    paths-ignore:
+      - '**.md'
 
 env:
   CARGO_TERM_COLOR: always

module-system/README.md

@@ -29,8 +29,9 @@ pub struct Bank<C: sov_modules_api::Context> {
 }
 ```
 
-At first glance, this definition might seem a little bit intimidating because of the generic `C`. Don't worry, we'll explain that
-generic in detail later. For now, just notice that a module is a struct with an address and some `#[state]` fields specifying
+At first glance, this definition might seem a little bit intimidating because of the generic `C`.
+Don't worry, we'll explain that generic in detail later.
+For now, just notice that a module is a struct with an address and some `#[state]` fields specifying
 what kind of data this module has access to. Under the hood, the `ModuleInfo` derive macro will do some magic to ensure that
 any `#[state]` fields get mapped onto unique storage keys so that only this particular module can read or write its state values.
 
@@ -175,7 +176,7 @@ pub trait Spec {
 
 As you can see, a `Spec` for a rollup specifies the concrete types that will be used for many kinds of cryptographic operations.
 That way, you can define your business logic in terms of _abstract_ cryptography, and then instantiate it with cryptography which
-is efficient in your particular choice of zkvm.
+is efficient in your particular choice of ZKVM.
 
 In addition to the `Spec` trait, the Module System provides a simple `Context` trait which is defined like this:
 
@@ -191,7 +192,7 @@ pub trait Context: Spec + Clone + Debug + PartialEq {
 Modules are expected to be generic over the `Context` type. This trait gives them a convenient handle to access all of the cryptographic operations
 defined by a `Spec`, while also making it easy for the Module System to pass in authenticated transaction-specific information which
 would not otherwise be available to a module. Currently, a `Context` is only required to contain the `sender` (signer) of the transaction,
-but this trait might be extended in future.
+but this trait might be extended in the future.
 
 Putting it all together, recall that the Bank struct is defined like this.