Addressing docs translation glitch #7687- fixes adding-static-pages and configuring-search-fields

[archaeogeek]

Addressing two-character literal doc translation glitch (PR #7687)

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

[jodygarnett]

@archaeogeek you asked for a review, but this does not appear ready, or are you doing these a bit at time?

See also #7687

[jodygarnett]

This looks good thus far, I will merge and backport, and mark these 4 files "done" with respect to the list on https://github.com/geonetwork/core-geonetwork/pull/7687/files

That PR is on a public core-geonetwork/docs-glitch branch if you wish to contribute directly to the PR.