fix: generate previews from forked repos

.github/workflows/pull_request.yml

@@ -1,13 +1,17 @@
 name: Pull request workflow
 
 on:
-  pull_request:
+  pull_request_target:
+    types:
+      - opened
+      - reopened
+      - synchronize
     branches:
-      - '*'
+      - 'main'
+      - 'dev'
 
-#  push:
-#    branches:
-#      - main
+permissions:
+  contents: write
 
 jobs:
 
@@ -24,7 +28,7 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v2
         with:
-          node-version: 16
+          ref: refs/pull/${{ github.event.pull_request.number }}/merge
 
       - name: Install Node.js
         uses: actions/setup-node@v2
@@ -53,9 +57,8 @@ jobs:
       - name: Checkout repository
         uses: actions/checkout@v2
         with:
-          node-version: 16
           ref: gh-pages
-          USER_TOKEN: ${{ secrets.USER_TOKEN }}
+          token: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Extract PR details
         id: pr
@@ -88,9 +91,9 @@ jobs:
           ls -al
           echo "Git status:"
           git status
-
           git config user.name "GitHub Actions"
           git config user.email noreply@github.com
+
           git add .
 
 
@@ -105,7 +108,7 @@ jobs:
 
             # Commit changes
             git commit -m "$commit_message"
-          
+
             # Check if commit was successful
             if [ $? -eq 0 ]; then
               # Debug information
@@ -140,5 +143,4 @@ jobs:
           echo "Your preview build is ready! ✨ Check the following link in 1-2 minutes: https://starknet-io.github.io/starknet-docs/${{ steps.pr.outputs.PR_ID }}/documentation/ ." >/tmp/comment
           gh pr comment ${{ github.event.pull_request.number }} -F /tmp/comment
         env:
-          # USER_TOKEN: "${{ secrets.USER_TOKEN }}"
           GH_TOKEN: "${{ github.token }}"

_typos.toml

@@ -5,3 +5,7 @@ check-file = false
 extend-glob = ["*.adoc"]
 check-file = true
 
+[default.extend-words]
+# Don't correct the word
+afe = "afe"
+

components/Starknet/modules/architecture_and_concepts/pages/Smart_Contracts/serialization_of_Cairo_types.adoc

@@ -1,7 +1,7 @@
 [id="serialization_of_types_in_Cairo"]
 = Serialization of Cairo types
 
-When you interact with contracts, especially if you are a library or SDK developer that wants to construt transactions, you need to understand how Cairo handles types that are larger than 252 bits so you can correctly formulate the calldata in a transaction.
+When you interact with contracts, especially if you are a library or SDK developer that wants to construct transactions, you need to understand how Cairo handles types that are larger than 252 bits so you can correctly formulate the calldata in a transaction.
 
 The field element (`felt252`), which contains 252 bits, is the only actual type in the Cairo VM. So all high-level Cairo types that are larger than 252 bits, such as `u256` or arrays, are ultimately represented by a list of felts. In order to interact with a contract, you need to know how to encode its arguments as a list of felts so you can correctly formulate the calldata in the transaction.
 SDKs, such as starknet.js, encode the calldata for you, so you can simply specify any type and the SDK properly formulates the calldata. For example, you don’t need to know that a `u256` value is represented by two `felt252` values. You can simply specify a single integer in your code, and the SDK takes care of the serialization and encoding.