Change forc doc --manifest-path to forc doc --path

.github/workflows/ci.yml

@@ -233,7 +233,7 @@ jobs:
         run: |
           cargo install --locked --debug --path ./forc-plugins/forc-doc
       - name: Build sway-lib-std docs
-        run: forc doc --manifest-path ./sway-lib-std
+        run: forc doc --path ./sway-lib-std
 
   build-forc-test-project:
     runs-on: ubuntu-latest

.github/workflows/gh-pages.yml

@@ -50,7 +50,7 @@ jobs:
         run: mdbook build docs/reference
 
       - name: Build Sway std library
-        run: forc doc --manifest-path ./sway-lib-std
+        run: forc doc --path ./sway-lib-std
 
       - name: Deploy master std
         uses: peaceiris/actions-gh-pages@v3

ci_checks.sh

@@ -48,5 +48,5 @@ echo "[workspace]" >> test-proj/Cargo.toml &&
 rm -R test-proj &&
 cargo run --locked --release --bin test -- --target evm --locked &&
 cargo run --locked -p forc -- build --locked --path ./test/src/sdk-harness &&
-cargo test --locked --manifest-path ./test/src/sdk-harness/Cargo.toml -- --nocapture &&
+cargo test --locked --path ./test/src/sdk-harness/Cargo.toml -- --nocapture &&
 cargo run --locked --release --bin test -- --locked

forc-plugins/forc-doc/README.md

@@ -78,7 +78,7 @@ $ cargo install --path forc-plugins/forc-doc
 Great! Let's check everything is working as intended. Try running `forc doc` on one of the test directories:
 
 ```sh
-$ forc doc --manifest-path src/tests/data/impl_traits --open
+$ forc doc --path src/tests/data/impl_traits --open
 ```
 
 If it succeeded, you should be seeing the test docs in your browser.

forc-plugins/forc-doc/src/cli.rs

@@ -23,7 +23,7 @@ pub struct Command {
     /// Path to the Forc.toml file. By default, forc-doc searches for the Forc.toml
     /// file in the current directory or any parent directory.
     #[clap(long)]
-    pub manifest_path: Option<String>,
+    pub path: Option<String>,
     /// Include non-public items in the documentation.
     #[clap(long)]
     pub document_private_items: bool,