[autofix.ci] apply automated fixes

Author: autofix-ci[bot]

src/pages/core/entrypoints/query.mdx

@@ -6,9 +6,9 @@ import { Callout } from "nextra/components";
 
 # Query
 
-In the previous section we talked about the [`execute`](./execute.mdx) endpoint. The `query` endpoint is
-actually pretty similar to its sibling `execute`, but with one key difference: The storage is only
-accessible immutably.
+In the previous section we talked about the [`execute`](./execute.mdx) endpoint. The `query`
+endpoint is actually pretty similar to its sibling `execute`, but with one key difference: The
+storage is only accessible immutably.
 
 This means you can only _read_ from the storage but not _write_ to it.
 
@@ -55,4 +55,3 @@ pub fn query(
   Ok(QueryResponse::default())
 }
 ```
-

src/pages/cw-multi-test/getting-started/counter/counter-sylvia.mdx

@@ -347,8 +347,8 @@ More details about the [Item](../../../cw-storage-plus/containers/item.mdx) type
 integer representing a counter value.
 
 More detailed explanation of the smart contract structure written in Sylvia can be found in
-[Sylvia documentation](../../../sylvia/basics/contract-structure.mdx), but for testing purposes we will
-just mention the key elements of this contract.
+[Sylvia documentation](../../../sylvia/basics/contract-structure.mdx), but for testing purposes we
+will just mention the key elements of this contract.
 
 #### constructor
 

src/pages/tutorial/cw-contract/good-practices.mdx

@@ -295,8 +295,8 @@ so that one can generate schema calling simply `cargo schema`.
 
 ## Disabling entry points for libraries
 
-Since we added the "rlib" target to the contract, it is now, as previously mentioned,
-usable as a dependency. The problem is that the contract dependent on ours would have Wasm entry points
+Since we added the "rlib" target to the contract, it is now, as previously mentioned, usable as a
+dependency. The problem is that the contract dependent on ours would have Wasm entry points
 generated twice - once in the dependency and once in the final contract. We can work this around by
 disabling generating Wasm entry points for the contract if the crate is used as a dependency. We
 would use [feature flags](https://doc.rust-lang.org/cargo/reference/features.html) for that.