Update Journal abbreviations page to correspond to the new funtionality

[BOgdAnSAM-sudo]

User description

This changes should only be merged after JabRef/jabref#14850 is merged.

---

PR Type

Documentation

---

Description

• Update journal abbreviations documentation to reflect new UI structure

• Replace old menu path with new Quality → Clean up entries workflow

• Update action names to match current implementation options

• Clarify available abbreviation and unabbreviation choices

---

Diagram Walkthrough

flowchart LR
  A["Old Menu Structure"] -- "replaced by" --> B["Quality → Clean up entries → Journal-related"]
  C["Old Action Names"] -- "updated to" --> D["New Action Options"]
  D --> E["Abbreviate/Dotless/Shortest/Unabbreviate/No changes"]

Loading

File Walkthrough

Relevant files

Documentation

journalabbreviations.md Update journal abbreviations menu path and action names    en/advanced/journalabbreviations.md Updated menu navigation path from direct Quality menu to Quality → Clean up entries → Journal-related → Manage journal abbreviations Replaced old action names with new ones: DEFAULT, MEDLINE, SHORTEST UNIQUE now map to Abbreviate (default), Abbreviate (dotless), Abbreviate (shortest unique) Added new action option "No changes" to the available choices Clarified workflow by specifying dropdown menu selection after navigating to the new location +1/-1

---

[qodo-free-for-open-source-projects]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-free-for-open-source-projects]

PR Code Suggestions ✨

No code suggestions found for the PR.