DOCSP-38064 - Arrays

[mongoKart]

The scope of this PR got pretty large. Basically:

• Moved Replace to its own page
• Moved Update One and Update Many to their own pages, each with an Arrays and Fields subpage
• Used substitutions for repeated content

The Fields page doesn't have code examples yet, but I'll create another ticket instead of adding it onto this one. I considered using collapsible elements on some of the pages, but didn't; let me know if you think that would be better.

Pull Request Info

PR Reviewing Guidelines

JIRA - https://jira.mongodb.org/browse/DOCSP-38064

Staging Links

fundamentals/crud/write-operations/replace

fundamentals/crud/write-operations/update-many

fundamentals/crud/write-operations/update-many/arrays

fundamentals/crud/write-operations/update-many/fields

fundamentals/crud/write-operations/update-one

fundamentals/crud/write-operations/update-one/arrays

fundamentals/crud/write-operations/update-one/fields

fundamentals/crud/write-operations

fundamentals/crud/write-operations/bulk-write

quick-reference

upgrade/v2

Self-Review Checklist

• Is this free of any warnings or errors in the RST?
• Did you run a spell-check?
• Did you run a grammar-check?
• Are all the links working?
• Are the facets and meta keywords accurate?

[netlify]

✅ Deploy Preview for mongodb-docs-csharp ready!

Name	Link
🔨 Latest commit	b1a0b01
🔍 Latest deploy log	https://app.netlify.com/sites/mongodb-docs-csharp/deploys/676586e898b57600085fdd68
😎 Deploy Preview	https://deploy-preview-295--mongodb-docs-csharp.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

The backport to v2.30 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.30 v2.30
# Navigate to the new working tree
cd .worktrees/backport-v2.30
# Create a new branch
git switch --create backport-295-to-v2.30
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a2a9e5deeb7af434a687dc1ff993d532c145d8e3
# Push it to GitHub
git push --set-upstream origin backport-295-to-v2.30
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.30

Then, create a pull request where the base branch is v2.30 and the compare/head branch is backport-295-to-v2.30.

[github-actions]

The backport to v2.29 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.29 v2.29
# Navigate to the new working tree
cd .worktrees/backport-v2.29
# Create a new branch
git switch --create backport-295-to-v2.29
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a2a9e5deeb7af434a687dc1ff993d532c145d8e3
# Push it to GitHub
git push --set-upstream origin backport-295-to-v2.29
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.29

Then, create a pull request where the base branch is v2.29 and the compare/head branch is backport-295-to-v2.29.

[github-actions]

The backport to v2.28 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.28 v2.28
# Navigate to the new working tree
cd .worktrees/backport-v2.28
# Create a new branch
git switch --create backport-295-to-v2.28
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a2a9e5deeb7af434a687dc1ff993d532c145d8e3
# Push it to GitHub
git push --set-upstream origin backport-295-to-v2.28
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.28

Then, create a pull request where the base branch is v2.28 and the compare/head branch is backport-295-to-v2.28.

[github-actions]

The backport to v2.27 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.27 v2.27
# Navigate to the new working tree
cd .worktrees/backport-v2.27
# Create a new branch
git switch --create backport-295-to-v2.27
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a2a9e5deeb7af434a687dc1ff993d532c145d8e3
# Push it to GitHub
git push --set-upstream origin backport-295-to-v2.27
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.27

Then, create a pull request where the base branch is v2.27 and the compare/head branch is backport-295-to-v2.27.

[github-actions]

The backport to v2.26 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.26 v2.26
# Navigate to the new working tree
cd .worktrees/backport-v2.26
# Create a new branch
git switch --create backport-295-to-v2.26
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a2a9e5deeb7af434a687dc1ff993d532c145d8e3
# Push it to GitHub
git push --set-upstream origin backport-295-to-v2.26
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.26

Then, create a pull request where the base branch is v2.26 and the compare/head branch is backport-295-to-v2.26.

[github-actions]

The backport to v2.25 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.25 v2.25
# Navigate to the new working tree
cd .worktrees/backport-v2.25
# Create a new branch
git switch --create backport-295-to-v2.25
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a2a9e5deeb7af434a687dc1ff993d532c145d8e3
# Push it to GitHub
git push --set-upstream origin backport-295-to-v2.25
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.25

Then, create a pull request where the base branch is v2.25 and the compare/head branch is backport-295-to-v2.25.

[github-actions]

The backport to v2.24 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.24 v2.24
# Navigate to the new working tree
cd .worktrees/backport-v2.24
# Create a new branch
git switch --create backport-295-to-v2.24
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a2a9e5deeb7af434a687dc1ff993d532c145d8e3
# Push it to GitHub
git push --set-upstream origin backport-295-to-v2.24
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.24

Then, create a pull request where the base branch is v2.24 and the compare/head branch is backport-295-to-v2.24.

[github-actions]

The backport to v2.23 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.23 v2.23
# Navigate to the new working tree
cd .worktrees/backport-v2.23
# Create a new branch
git switch --create backport-295-to-v2.23
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a2a9e5deeb7af434a687dc1ff993d532c145d8e3
# Push it to GitHub
git push --set-upstream origin backport-295-to-v2.23
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.23

Then, create a pull request where the base branch is v2.23 and the compare/head branch is backport-295-to-v2.23.

[github-actions]

The backport to v2.22 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-v2.22 v2.22
# Navigate to the new working tree
cd .worktrees/backport-v2.22
# Create a new branch
git switch --create backport-295-to-v2.22
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 a2a9e5deeb7af434a687dc1ff993d532c145d8e3
# Push it to GitHub
git push --set-upstream origin backport-295-to-v2.22
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-v2.22

Then, create a pull request where the base branch is v2.22 and the compare/head branch is backport-295-to-v2.22.